Re: [PATCH RFC] ata: Intel IDE-R support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> I don't really think it would be dangerous to grab intel IDE
> controllers with ata_generic.  Again, that's what windows would do.
> And for sysfs unbind case, if the user specifically unbinds the
> controller from ata_piix, what is broken?

If the user changes the PCI id list what happens ?

> 
> > The extreme example would be if you have ata_generic binding to all
> > devices and you forgot to compile in RZ1000 support. On the relevant
> > board that just ate your file system.
> > 
> > So the grab it all approach was dismissed.
> 
> For RZ1000, sure, but we're talking about only intel IDEs here.

I don't know. I do know what the Intel folks have told me about detecting
them.

> > 0xF8 is non zero on all later Intel ATA PCI chipsets
> > 0x40 is writable on all earlier Intel ATA PCI chipsets, and zero + non
> > writable on the IDE-R devices.
> 
> Maybe it's okay now but who's gonna remember what's going on there
> after five years and nobody guarantees the above would continue to

Add a comment ?

> hold in the future.

It did occur to me to check this would be true in the future. Either way
- an id table would go out of date more often.

Alan

--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Filesystems]     [Linux SCSI]     [Linux RAID]     [Git]     [Kernel Newbies]     [Linux Newbie]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Samba]     [Device Mapper]

  Powered by Linux