Skip to contentSkip to conversation

SATA support merge in 2.4.27

DISCUSSION Andi Kleen 4 participants 5 messages Apr 15, 2004 – Apr 16, 2004 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

Andi Kleen

author
#1 lore raw
Quoted 9 lines · Marcelo Tosatti

Jeff Garzik sent me a SATA update to be merged in 2.4.x.

A lot of new boxes are shipping with SATA-only disks, and its pretty bad to not have a "stable" series without such industry-standard support.

This is the last feature to be merged on 2.4.x, and only because its quite necessary.

Any oppositions?

The big problem is that the SATA code will move some disks from /dev/hdX to /dev/sdX (e.g. most disks in modern intel chipsets) And then the boxes don't boot anymore. It's probably a bad idea to merge it.

-Andi

#2 lore raw
Quoted 10 lines · Andi Kleen
Quoted 8 lines · Marcelo Tosatti

Jeff Garzik sent me a SATA update to be merged in 2.4.x.

A lot of new boxes are shipping with SATA-only disks, and its pretty bad to not have a "stable" series without such industry-standard support.

This is the last feature to be merged on 2.4.x, and only because its quite necessary.

Quoted 6 lines
Quoted 1 line

Any oppositions?

The big problem is that the SATA code will move some disks from /dev/hdX to /dev/sdX (e.g. most disks in modern intel chipsets) And then the boxes don't boot anymore. It's probably a bad idea to merge it.

This statement is false for the majority of the SATA drivers.

Further, ata_piix is not included in the merge.

Jeff

#3 lore raw
In reply to Andi Kleen
Quoted 10 lines · Andi Kleen
Quoted 8 lines · Marcelo Tosatti

Jeff Garzik sent me a SATA update to be merged in 2.4.x.

A lot of new boxes are shipping with SATA-only disks, and its pretty bad to not have a "stable" series without such industry-standard support.

This is the last feature to be merged on 2.4.x, and only because its quite necessary.

Quoted 6 lines
Quoted 1 line

Any oppositions?

The big problem is that the SATA code will move some disks from /dev/hdX to /dev/sdX (e.g. most disks in modern intel chipsets) And then the boxes don't boot anymore. It's probably a bad idea to merge it.

Oh, this is also false for all the distro users which are _already_ using /dev/sdX for their disks.

They _have_ to patch in libata, otherwise the upstream kernel will break their disks by changing them from /dev/hdX to /dev/sdX.

Another problem is that the upstream /dev/hdX driver locks up for a many users, where libata does not.

Jeff

#4 lore raw
In reply to Andi Kleen
Quoted 9 lines · Andi Kleen
Quoted 8 lines · Marcelo Tosatti

Jeff Garzik sent me a SATA update to be merged in 2.4.x.

A lot of new boxes are shipping with SATA-only disks, and its pretty bad to not have a "stable" series without such industry-standard support.

This is the last feature to be merged on 2.4.x, and only because its quite necessary.

Quoted 6 lines
Quoted 1 line

Any oppositions?

The big problem is that the SATA code will move some disks from /dev/hdX to /dev/sdX (e.g. most disks in modern intel chipsets) And then the boxes don't boot anymore. It's probably a bad idea to merge it.

ICH5 SATA and SiI3112 are the only affected chipsets. You don't have to enable libata drivers for them or their PCI IDs can be removed from the libata drivers if needed.

Bartlomiej

#5 lore raw
Quoted 3 lines · Bartlomiej Zolnierkiewicz

ICH5 SATA and SiI3112 are the only affected chipsets. You don't have to enable libata drivers for them or their PCI IDs can be removed from the libata drivers if needed.

Hmm, do you mean that existent SATA drives on current 2.4.x kernels where "seen" as /dev/hdX and with the SATA merge will be /dev/sdX ? I dont think 2.4.x supported SATA (at least not on Intel). I have a ICH5 motherboard with one PATA drive and one SATA drive. With 2.6.5 kernel with support for IDE PIIX (in the ATA section) and SATA PIIX (in the SCSI low level drivers section) I see my PATA as /dev/hda and my SATA as /dev/sdb (I have another SCSI disk on a SCSI controller which is /dev/sda). So it does seem to me to do the right thing. Also on 2.4.25 with PIIX support I only saw the PATA disk. In BIOS the PATA/SATA configuration is set to "Enhanced". More informations:

ICH5: IDE controller at PCI slot 0000:00:1f.1
ICH5: chipset revision 2
ICH5: not 100% native mode: will probe irqs later

00:1f.1 IDE interface: Intel Corp.: Unknown device 25a2 (rev 02) (prog-if 8a [Master SecP PriP])
Subsystem: Intel Corp.: Unknown device 342f
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 18
Region 0: I/O ports at <unassigned>
Region 1: I/O ports at <unassigned>
Region 2: I/O ports at <unassigned>
Region 3: I/O ports at <unassigned>
Region 4: I/O ports at fc00 [size=16]
Region 5: Memory at 40000000 (32-bit, non-prefetchable) [size=1K]

00:1f.2 IDE interface: Intel Corp.: Unknown device 25a3 (rev 02) (prog-if 8f [Master SecP SecO PriP PriO])
Subsystem: Intel Corp.: Unknown device 342f
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B-
Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
Interrupt: pin A routed to IRQ 18
Region 0: I/O ports at ec00 [size=8]
Region 1: I/O ports at e800 [size=4]
Region 2: I/O ports at e400 [size=8]
Region 3: I/O ports at e000 [size=4]
Region 4: I/O ports at dc00 [size=16]

Quoted 1 line

Bartlomiej

Signature · 3 lines
Mihai RUSU                                    Email: [email protected]
GPG : http://dizzy.roedu.net/dizzy-gpg.txt    WWW: http://dizzy.roedu.net
                       "Linux is obsolete" -- AST