Skip to contentSkip to conversation

sata & scsi suggestion for make menuconfig

DISCUSSION Bodo Eggert 3 participants 3 messages Sep 8, 2007 3 messages 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]

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

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

#3 lore raw
Quoted 6 lines · Al Boldi
Quoted 4 lines · Alan Cox
Quoted 1 line

I once sent a patch to make libata a submenu of scsi.

Which is wrong

Quoted 7 lines
Quoted 5 lines

The general comments about moving this stuff around and making it clearer what sd/sr etc are nowdays are good but hiding libata under SCSI will cause even more confusion than it cures

That's easy to fix: just change the SCSI heading to include a libata hint.

I think you're fixing the wrong problem.

The real problem is hiding devices attached to some controlers between one kind of the controllers. This has been correct whern they were bus- specific, but since they are now shared by three busses, they should get their own menu called "(S)ATA/USB/SCSI attached devices" - or whatever a native speaker would suggest.

Besides that, if I imagine being a semi-novice and searching for IDE support, I would have a hard time finding the IDE menu, and asuming PATA to be non-experimental one day, I'd have a hard time deciding which of the drivers to use. Maybe the SATA-drivers should be put above the old PATA menu, amd maybe both of the titles should include "(E)IDE"?

BTW: For CONFIG_ATA, you can replace
"(!M32R && !M68K || BROKEN) && (!SUN4 || BROKEN)"
with "(!M32R && !M68K && !SUN4 || BROKEN)"

BTW2: I think that menu needs very much reordering. "Block devices" should be renamed to "Other block devices", AGP support should belong into graphics support, and many other things I don't even know need to be pushed around. Even ordering by name would be better than the current situation! But it should be done by someone knowing these devices, I could only do a part.

Signature · 4 lines
Top 100 things you don't want the sysadmin to say:
14. Any more trouble from you and your account gets moved to the 750

Friß, Spammer: [email protected]
#4 lore raw
Quoted 5 lines · Bodo Eggert

The real problem is hiding devices attached to some controlers between one kind of the controllers. This has been correct whern they were bus- specific, but since they are now shared by three busses, they should get their own menu called "(S)ATA/USB/SCSI attached devices" - or whatever a native speaker would suggest.

A side note: SCSI is not a bus. It is an architecture and a set of implementation standards; including command set standards, transport protocol standards and interconnect standards for a whole lot of different applications, transports, and interconnects, and not all of the latter are actual buses. The oldest of SCSI interconnects, SCSI Parallel Interconnect alias SPI, is often mistaken for all of SCSI even though its role is diminishing. There is much more:
http://www.t10.org/scsi-3.htm

You are right though that Linux' SCSI command set drivers and SCSI core are used for non-SCSI transports too, and this is not very well reflected by the configuration menu layout. (But is there an ideal menu layout? I'm sure there isn't.)

Signature · 3 lines
Stefan Richter
-=====-=-=== =--= -=---
http://arcgraph.de/sr/
#5 lore raw
In reply to Bodo Eggert
Quoted 5 lines · On Sat, 08 Sep 2007 18:52:35 +0200 Bodo Eggert wrote:

BTW2: I think that menu needs very much reordering. "Block devices" should be renamed to "Other block devices", AGP support should belong into graphics support, and many other things I don't even know need to be pushed around. Even ordering by name would be better than the current situation! But it should be done by someone knowing these devices, I could only do a part.

how's this?

for 2.6.16-rc4: consolidated graphics config:
http://marc.info/?l=linux-kernel&m=114101236918589&w=2

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***