On Tue, Apr 15, 2008 at 01:29:37PM +0200, Manuel Bouyer wrote:
> On Mon, Apr 14, 2008 at 01:59:45PM -0700, Brian Buhrow wrote:
> > 2. If not, has anyone looked at what changes are required to make this
> > functionality work?
>
> For controllers exposing the native SATA interface, I'm not sure yet
> what would the best way of doing it. The PHY will signal devices going
> in and out and we could use this, just as with USB. But this could mean that
> a trancient connection error could end up with a drive going away and
> back, which is bad for the system (for the system this would just be a new
> drive, and mounted filesystems wouldn't be connected to the drive any
> more).
> The other option is to implement an atactl detach/scan, just as scsictl
> does. I started working on this some years ago and some bits are there.
> I didn't complete it because I didn't find a sane way to handle a rescan of
> a PATA bus with master/slave, with one of the devices already present.
> As SATA is p2p, this makes this part easier.
What about what the IEEE 1394 subsystem does at least with
sbp(4) devices? The bus has to be reset a few times before
an attached sbp(4) disappears.
Jonathan Kollasch
Attachment:
pgpZ9ND8R0Eb3.pgp
Description: PGP signature