Messages in this thread |  | | Date | Fri, 30 Aug 2002 08:51:26 +0200 | From | Vojtech Pavlik <> | Subject | Re: Hangs in 2.4.19 and 2.4.20-pre5 (IDE-related?) |
| |
On Thu, Aug 29, 2002 at 11:31:39PM -0700, Andre Hedrick wrote: > > Vojtech, > > Ball is in your court, DO IT! > Lets see what you got and how we can debloat the driver more. > > Looking to put the past behind, will you help?
Sure.
> Cheers, > > Andre Hedrick > LAD Storage Consulting Group > > > On Fri, 30 Aug 2002, Vojtech Pavlik wrote: > > > > Well if atapci is that complete then I see no reason to keep proc about. > > > So if it needs to go we delete it. > > > > I think you can drop the chipset specific /proc code. It'll simplify the > > drivers a lot as well as making them smaller. > > > > On the other hand, I'd suggest that some generic /proc code is put in > > place instead of the chipset-specific one - the values that cannot be > > read from PCI config registers, like: > > > > The PIO/MMIO/(U)DMA mode (and transfer rate) the IDE driver is operating > > the in. The bus speed the driver thinks is running at. Whether the IDE > > driver has detected a 80 or 40 wire cable. Etc, etc. This would be very > > useful, can be done by a single common routine, and most users actually > > don't need the exact timings.
-- Vojtech Pavlik SuSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |