Date: Tue, 26 Sep 2017 22:52:28 +0200 From: Tomasz CEDRO <tomek@cedro.info> To: Polytropon <freebsd@edvax.de> Cc: FreeBSD Questions Mailing List <freebsd-questions@freebsd.org>, "freebsd-usb@FreeBSD.org" <freebsd-usb@freebsd.org>, freebsd-hardware@freebsd.org Subject: Re: USB Device self-umount Message-ID: <CAFYkXjmMEo13TLyP8cv%2BbmDTz_UfHz%2BeN_FkxJ1hvUFnOfZRRw@mail.gmail.com> In-Reply-To: <20170926200308.5a9fb785.freebsd@edvax.de> References: <CAFYkXjnP7Ha_uZxc1zF0pz_7C3OdsJ3h-H8uyZQE_ViX5=YzBQ@mail.gmail.com> <20170926200308.5a9fb785.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hey Polytropon! :-) Thanks for ideas! I am at the moment at point where I sniff out the USB traffic and analyze SCSI packets.. and also I got into SCSI specification to search for some possibilities.. :-) I will have to see how Windoze handles ATAPI EJECT, maybe that could bring some insight on how to umount ejectable media triggered by the device-eject-button-press.. As for now the device reports CHECK-CONDITION to mark media missing, then reboots and re-appeares, but that causes "device not cleanly unmounted" warnings on macOS for instance.. Will report back when I find anything interesting :-) Best regards! :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFYkXjmMEo13TLyP8cv%2BbmDTz_UfHz%2BeN_FkxJ1hvUFnOfZRRw>