On Thu, May 04, 2006 at 04:28:42PM +0100, Alan Cox wrote: > > > Since you've been busy I didn't want to bother you, but now that you > > mention your PATA efforts again, is there a git tree to pull from, > > which contains code similar to that in the latest patches? > > Not for the current code. The core stuff is mostly in the tree now and > I'll try and push a patch some time today or tomorrow thats versus > 2.6.17-rc and should match. > Sounds great! I'll build new kernels for all my boxes as soon as I can get a hold on said patch. At least it "felt" cleaner and I/O was a little less of a handbrake using libata, so I'll go for it once again. Just one more thing, I had to hack a little on Kconfig files to make the "newer" promise driver available - if my memory doesn't fail me I sent a patch, more like a RFC. Are some drivers intentionally left out of Kbuild? I could not trigger any problem so far, using ata_piix on this laptop, and pata_via / pata_pdc2027x on my desktop. The only strangeness I had was some windoze firmware upgrade tool for my ATAPI CDRW drive running in wine, poking on every sg device in existence, thus triggering a freeze as it messed with the disks in some wicked way. But since this was never intended to work in the first place, I was happy with it working after simply deleting all sg devs corresponding with disks. And I guess it is worth mentioning that the SCSI IOCTLs in question are only accepted by the SCSI stack when the process is run as root, so it's not exactly something anybody could try on a machine he cannot already kill. Attempts to run this as an ordinary user would make the firmware tool get stuck with an all-empty progress bar, and the wine processes were easily TERM-able. If there's anything I might want to try out or you'd want to know, like lspci output and such, please let me know. I'm not home right now, but here goes for starters. lspci excerpt: 00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) (prog-if 80 [Master]) lspci -vvvxxxn excerpt: 00:07.1 0101: 8086:7111 (rev 01) (prog-if 80) 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: 32 Region 4: I/O ports at 0860 [size=16] 00: 86 80 11 71 05 00 80 02 01 80 01 01 00 20 00 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 61 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 40: 07 e3 07 e3 00 00 00 00 01 00 02 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f0: 00 00 00 00 00 00 00 00 30 0f 00 00 00 00 00 00 This one has been working perfectly so far, on an ancient Dell Latitude CPiA. Kind regards, Chris
Attachment:
pgpz74RUPDTMA.pgp
Description: PGP signature
- References:
- cdrom: a dirty CD can freeze your system
- From: Herbert Rosmanith <[email protected]>
- Re: cdrom: a dirty CD can freeze your system
- From: Alan Cox <[email protected]>
- Re: cdrom: a dirty CD can freeze your system
- From: Christian Trefzer <[email protected]>
- Re: cdrom: a dirty CD can freeze your system
- From: Alan Cox <[email protected]>
- cdrom: a dirty CD can freeze your system
- Prev by Date: Re: limits / PIPE_BUF?
- Next by Date: Re: limits / PIPE_BUF?
- Previous by thread: Re: cdrom: a dirty CD can freeze your system
- Next by thread: Re: cdrom: a dirty CD can freeze your system
- Index(es):