Re: IRQ problem with PCMCIA
Alan, The old code can be fixed, just I don't have the time or any desire to look at it again, still. The burn out from the last issues from 2001-2003, cost me some health problems over the stress. If I encounter these problems and become annoyed enough, I will fix it. However, if it is cheaper to buy working hardware, that is the route I will take. You (Alan), if anyone knows anything can be done in Linux, otherwise none of us would have ever put this much effort into its success. Cheers, Andre On Mon, 22 Aug 2005, Alan Cox wrote: > On Llu, 2005-08-22 at 11:25 +0200, Bartlomiej Zolnierkiewicz wrote: > > CardBus IDE devices work just fine but there are still issues with > > hotplug support (work in progress). > > "work in progress". Yes because I submitted working IDE cardbus hotplug > support, and Mark Lord submitted a Delkin driver both of which worked > months ago rather nicely and neither of which hit the Bartlomiej stone > wall and never got in and are now stale patches. > > > > up ever getting those into the kernel. Please wait instead for the new > > > SATA/ATA layer to develop hotplug support. > > > > This is just a FUD to discourage people from working on IDE drivers. > > Alan is doing this on purpose and doesn't really want to improve things. > > Its a realistic assessment based upon over ten years working on the > Linux kernel. I do not believe you are capable of fixing the old IDE > code. But don't take that personally I am sceptical than anyone can fix > the old IDE code. > > Alan > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: IRQ problem with PCMCIA
Alan, The old code can be fixed, just I don't have the time or any desire to look at it again, still. The burn out from the last issues from 2001-2003, cost me some health problems over the stress. If I encounter these problems and become annoyed enough, I will fix it. However, if it is cheaper to buy working hardware, that is the route I will take. You (Alan), if anyone knows anything can be done in Linux, otherwise none of us would have ever put this much effort into its success. Cheers, Andre On Mon, 22 Aug 2005, Alan Cox wrote: On Llu, 2005-08-22 at 11:25 +0200, Bartlomiej Zolnierkiewicz wrote: CardBus IDE devices work just fine but there are still issues with hotplug support (work in progress). work in progress. Yes because I submitted working IDE cardbus hotplug support, and Mark Lord submitted a Delkin driver both of which worked months ago rather nicely and neither of which hit the Bartlomiej stone wall and never got in and are now stale patches. up ever getting those into the kernel. Please wait instead for the new SATA/ATA layer to develop hotplug support. This is just a FUD to discourage people from working on IDE drivers. Alan is doing this on purpose and doesn't really want to improve things. Its a realistic assessment based upon over ten years working on the Linux kernel. I do not believe you are capable of fixing the old IDE code. But don't take that personally I am sceptical than anyone can fix the old IDE code. Alan - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: IT8212/ITE RAID
WHOA Gents! Let me get some popcorn to watch this p-contest. The way you guys are sniping at each other sounds like the good-old days, when everyone railed me and the subsystem and ended up railing back Guess nothing was learned from the 6+ years of flamage. I have mellowed out with age ... Bart, give Alan a break ... his is genrally right at the end of the day. Alan, give Bart a break ... cause there is no way I am coming back for a three-pete. Cheers, Andre On Mon, 22 Aug 2005, Bartlomiej Zolnierkiewicz wrote: > Any news about URLs? It shouldn't be too hard find them unless they > never existed in the first place. I will work on the issues immediately. > > Bartlomiej > > On 8/14/05, Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> wrote: > > On 8/14/05, Alan Cox <[EMAIL PROTECTED]> wrote: > > > On Sul, 2005-08-14 at 17:56 +0200, Bartlomiej Zolnierkiewicz wrote: > > > > * your stuff was accepted after all (and some stuff like ide-cd > > > > fixes was never splitted from the -ac patchset and submitted) > > > > > > They were. > > > > I remember discussion about end-of-media ide-cd fixes but the patch > > was never submitted. If you have *URL* to the patch I'll work on the patch. > > > > > > * you've never provided any technical details on "the stuff I broke" > > > > > > I did, several times. I had some detailed locking discussions with > > > Manfred and others on it as a result. The locking in the base IDE is > > > still broken, in fact its become worse - the random locking around > > > timing changes now causes some PIIX users to see double spinlock debug > > > with the base kernel as an example. > > > > Huh? *WHICH* my patch causes this? > > > > I don't remember this discussion et all, care to give some pointers? > > > > > > > Would make sense, but I thought I had the right bits masked. Will > > > > > take a > > > > > > > > WIN_RESTORE is send unconditionally (as it always was), > > > > > > > > This is not the right thing, somebody should go over all ATA/ATAPI > > > > drafts and come with the correct strategy of handling WIN_RESTORE. > > > > > > Ok that would make sense. Matthew Garrett also reported some problems in > > > that area with suspend/resume (BIOS restoring its idea of things...) > > > > Quite likely, WIN_RESTORE is not sent on resume etc. > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: IT8212/ITE RAID
WHOA Gents! Let me get some popcorn to watch this p-contest. The way you guys are sniping at each other sounds like the good-old days, when everyone railed me and the subsystem and ended up railing back Guess nothing was learned from the 6+ years of flamage. I have mellowed out with age ... Bart, give Alan a break ... his is genrally right at the end of the day. Alan, give Bart a break ... cause there is no way I am coming back for a three-pete. Cheers, Andre On Mon, 22 Aug 2005, Bartlomiej Zolnierkiewicz wrote: Any news about URLs? It shouldn't be too hard find them unless they never existed in the first place. I will work on the issues immediately. Bartlomiej On 8/14/05, Bartlomiej Zolnierkiewicz [EMAIL PROTECTED] wrote: On 8/14/05, Alan Cox [EMAIL PROTECTED] wrote: On Sul, 2005-08-14 at 17:56 +0200, Bartlomiej Zolnierkiewicz wrote: * your stuff was accepted after all (and some stuff like ide-cd fixes was never splitted from the -ac patchset and submitted) They were. I remember discussion about end-of-media ide-cd fixes but the patch was never submitted. If you have *URL* to the patch I'll work on the patch. * you've never provided any technical details on the stuff I broke I did, several times. I had some detailed locking discussions with Manfred and others on it as a result. The locking in the base IDE is still broken, in fact its become worse - the random locking around timing changes now causes some PIIX users to see double spinlock debug with the base kernel as an example. Huh? *WHICH* my patch causes this? I don't remember this discussion et all, care to give some pointers? Would make sense, but I thought I had the right bits masked. Will take a WIN_RESTORE is send unconditionally (as it always was), This is not the right thing, somebody should go over all ATA/ATAPI drafts and come with the correct strategy of handling WIN_RESTORE. Ok that would make sense. Matthew Garrett also reported some problems in that area with suspend/resume (BIOS restoring its idea of things...) Quite likely, WIN_RESTORE is not sent on resume etc. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] IDE disks show invalid geometries in /proc/ide/hd*/geometry
Did you read ATA-1 through ATA-7 to understand all the variations? On Tue, 2 Aug 2005, Mark Bellon wrote: > The ATA specification tells large disk drives to return C/H/S data of > 16383/16/63 regardless of their actual size (other variations on this > return include 15 heads and/or 4092 cylinders). Unfortunately these CHS > data confuse the existing IDE code and cause it to report invalid > geometries in /proc when the disk runs in LBA mode. > > The invalid geometries can cause failures in the partitioning tools; > partitioning may be impossible or illogical size limitations occur. This > also leads to various forms of human confusion. > > I attach a patch that fixes this problem while strongly attempting to > not break any existing side effects and await any comments. > > mark > > Signed-off-by: Mark Bellon <[EMAIL PROTECTED]> > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] IDE disks show invalid geometries in /proc/ide/hd*/geometry
Did you read ATA-1 through ATA-7 to understand all the variations? On Tue, 2 Aug 2005, Mark Bellon wrote: The ATA specification tells large disk drives to return C/H/S data of 16383/16/63 regardless of their actual size (other variations on this return include 15 heads and/or 4092 cylinders). Unfortunately these CHS data confuse the existing IDE code and cause it to report invalid geometries in /proc when the disk runs in LBA mode. The invalid geometries can cause failures in the partitioning tools; partitioning may be impossible or illogical size limitations occur. This also leads to various forms of human confusion. I attach a patch that fixes this problem while strongly attempting to not break any existing side effects and await any comments. mark Signed-off-by: Mark Bellon [EMAIL PROTECTED] - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Greg's Decree! (was Re: Linus' decrees?)
Greg, Linus is not always correct, sometimes his point of view is hard to see. My shoulders got in the way most of the time; however, Linus is consistant. Well until he changes his mind. Crack ?? Get some plumber's putty to smooth over the gap. Cheers, Andre Hedrick LAD Storage Consulting Group On Thu, 24 Feb 2005, Greg Folkert wrote: > On Thu, 2005-02-24 at 15:03 -0500, Stuart MacDonald wrote: > > Recently I ran across > > http://groups.google.ca/groups?hl=en=lang_en=off=1033074519.2698.5. > > camel%40localhost.localdomain > > > > Is there a collection point for Linus' decrees? > > > > The LSB (http://www.linuxbase.org/) seems to be mostly involved with > > how a distro is laid out, and not much to do with the kernel. > > Okay, Linus decreed... oh yeah. > > Exactly what is wrong with the method anyway? > > You on Crack? > > And no... that is not a decree in the traditional sense. It is more like > me saying: > "I decree that Linus Torvalds is the lead maintainer of the > Linux Kernel" > > Make TONS-O-SENSE to state the obvious. IOW the statement was all meant > to say *DO IT THIS WAY AND NO OTHER* as nobody else honors any other > method. > -- > greg, [EMAIL PROTECTED] > > The technology that is > Stronger, better, faster: Linux > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linus' decrees?
Stuart, Yeah! It is a road paved w/ X-maintainers ... AKA the the difference between the active maintainer list and the credit list. Cheers, Andre Hedrick LAD Storage Consulting Group On Thu, 24 Feb 2005, Stuart MacDonald wrote: > Recently I ran across > http://groups.google.ca/groups?hl=en=lang_en=off=1033074519.2698.5. > camel%40localhost.localdomain > > Is there a collection point for Linus' decrees? > > The LSB (http://www.linuxbase.org/) seems to be mostly involved with > how a distro is laid out, and not much to do with the kernel. > > ..Stu > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linus' decrees?
Stuart, Yeah! It is a road paved w/ X-maintainers ... AKA the the difference between the active maintainer list and the credit list. Cheers, Andre Hedrick LAD Storage Consulting Group On Thu, 24 Feb 2005, Stuart MacDonald wrote: Recently I ran across http://groups.google.ca/groups?hl=enlr=lang_ensafe=offselm=1033074519.2698.5. camel%40localhost.localdomain Is there a collection point for Linus' decrees? The LSB (http://www.linuxbase.org/) seems to be mostly involved with how a distro is laid out, and not much to do with the kernel. ..Stu - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Greg's Decree! (was Re: Linus' decrees?)
Greg, Linus is not always correct, sometimes his point of view is hard to see. My shoulders got in the way most of the time; however, Linus is consistant. Well until he changes his mind. Crack ?? Get some plumber's putty to smooth over the gap. Cheers, Andre Hedrick LAD Storage Consulting Group On Thu, 24 Feb 2005, Greg Folkert wrote: On Thu, 2005-02-24 at 15:03 -0500, Stuart MacDonald wrote: Recently I ran across http://groups.google.ca/groups?hl=enlr=lang_ensafe=offselm=1033074519.2698.5. camel%40localhost.localdomain Is there a collection point for Linus' decrees? The LSB (http://www.linuxbase.org/) seems to be mostly involved with how a distro is laid out, and not much to do with the kernel. Okay, Linus decreed... oh yeah. Exactly what is wrong with the method anyway? You on Crack? And no... that is not a decree in the traditional sense. It is more like me saying: I decree that Linus Torvalds is the lead maintainer of the Linux Kernel Make TONS-O-SENSE to state the obvious. IOW the statement was all meant to say *DO IT THIS WAY AND NO OTHER* as nobody else honors any other method. -- greg, [EMAIL PROTECTED] The technology that is Stronger, better, faster: Linux - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Patch for IDE hang after resetting quirk drive
Looks valid will take! Cheers, Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com On Tue, 3 Jul 2001, Dale Farnsworth wrote: > I have a Promise PDC20265 ide controller with one of the "quirk" drives, > a Quantum Fireballp LM30. That drive has a bad sector and accessing > it would result in a DMA timeout. Unfortunately, after the IDE driver > resets the controller, the drive never responded. > > The following patch appears to correct the problem. It duplicates > the workaround for "quirky" drives found in ide-features.c > > -Dale > > Dale Farnsworth [EMAIL PROTECTED] > > --- oldlinux-2.4.5/drivers/ide/ide.c Tue Jul 3 09:35:57 2001 > +++ linux-2.4.5/drivers/ide/ide.c Tue Jul 3 09:23:58 2001 > @@ -758,7 +758,10 @@ >*/ > OUT_BYTE(drive->ctl|6,IDE_CONTROL_REG); /* set SRST and nIEN */ > udelay(10); /* more than enough time */ > - OUT_BYTE(drive->ctl|2,IDE_CONTROL_REG); /* clear SRST, leave nIEN */ > + if (drive->quirk_list == 2) > + OUT_BYTE(drive->ctl, IDE_CONTROL_REG); /* clear SRST and nIEN */ > + else > + OUT_BYTE(drive->ctl|2,IDE_CONTROL_REG); /* clear SRST only */ > udelay(10); /* more than enough time */ > hwgroup->poll_timeout = jiffies + WAIT_WORSTCASE; > ide_set_handler (drive, _pollfunc, HZ/20, NULL); > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Patch for IDE hang after resetting quirk drive
Looks valid will take! Cheers, Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com On Tue, 3 Jul 2001, Dale Farnsworth wrote: I have a Promise PDC20265 ide controller with one of the quirk drives, a Quantum Fireballp LM30. That drive has a bad sector and accessing it would result in a DMA timeout. Unfortunately, after the IDE driver resets the controller, the drive never responded. The following patch appears to correct the problem. It duplicates the workaround for quirky drives found in ide-features.c -Dale Dale Farnsworth [EMAIL PROTECTED] --- oldlinux-2.4.5/drivers/ide/ide.c Tue Jul 3 09:35:57 2001 +++ linux-2.4.5/drivers/ide/ide.c Tue Jul 3 09:23:58 2001 @@ -758,7 +758,10 @@ */ OUT_BYTE(drive-ctl|6,IDE_CONTROL_REG); /* set SRST and nIEN */ udelay(10); /* more than enough time */ - OUT_BYTE(drive-ctl|2,IDE_CONTROL_REG); /* clear SRST, leave nIEN */ + if (drive-quirk_list == 2) + OUT_BYTE(drive-ctl, IDE_CONTROL_REG); /* clear SRST and nIEN */ + else + OUT_BYTE(drive-ctl|2,IDE_CONTROL_REG); /* clear SRST only */ udelay(10); /* more than enough time */ hwgroup-poll_timeout = jiffies + WAIT_WORSTCASE; ide_set_handler (drive, reset_pollfunc, HZ/20, NULL); - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Patch(2.4.5): Fix PCMCIA ATA/IDE freeze (w/ PCI add-in cards)V3
I should have known that you (instructor of the current and previous
maintainer) would have the answer off the top ;-)
Therefore by your description it mys be set always but I guess it is a
DGD; however, I do want to know that it is now.
Oh, and now that Big Drive Technology has been annouced I should finally
send you the code for 48-bit, sorry about the delay.
Cheers,
Andre Hedrick
ASL Kernel Development
Linux ATA Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035Web: www.aslab.com
On Fri, 29 Jun 2001 [EMAIL PROTECTED] wrote:
> Andre Hedrick wrote:
>
> > That is a legacy bit from ATA-2 but it is one of those things you cannot
> > get rid of :-(
>
> in ANSI X3.279-1996, "AT Attachment Interface with Extensions (ATA-2)",
> Approved September 11, 1996 , control register bit 3-7 are reserved.
>
> However ANSI X3.221-1994, "AT Attachment Interface for Disk Drives",
> Approved May 12, 1994, bit3 is "1" and bits 4-7 are "x".
> No further explanation.
>
> How far back must we go, to get the sense ?
>
> > struct {
> > unsigned bit0 : 1;
> > unsigned nIEN : 1;/* device INTRQ to host */
> > unsigned SRST : 1;/* host soft reset bit */
> > unsigned bit3 : 1;/* ATA-2 thingy */
> > unsigned reserved456: 3;
> > unsigned HOB: 1;/* 48-bit address ordering */
> > } control_t;
> >
> > once I add-in the real def of bit3 then I will not
> > need to look it up again.
>
> bit3: 0: drive has 1-8 heads
> 1: drive has more than 8 heads
>
> (From old MFM/RLL times. In ATA-1 bit3 is set to 1.
> See also
> http://www.win.tue.nl/~aeb/linux/hdtypes/hdtypes-2.html
> .)
>
> Andries
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Patch(2.4.5): Fix PCMCIA ATA/IDE freeze (w/ PCI add-in cards)V3
Okay my bad it is ATA-1 but even that does not explain the bit.
only that section 7.2.6 top of page 14 (index numbers) defines it to be
set to 1 with out a reason.
This this is a pre-ATA thing back in IDE.
If you really want to know the answer I can go dig it up, but later.
Cheers,
Andre Hedrick
ASL Kernel Development
Linux ATA Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035Web: www.aslab.com
On Fri, 29 Jun 2001, Gunther Mayer wrote:
> Andre Hedrick wrote:
> >
> > That is a legacy bit from ATA-2 but it is one of those things you can not
> > get rid of :-( even thou things are obsoleted, they are not retired.
> > This means that you have to go back into the past to see how it was used,
> > silly! I hope you agree to that point.
>
> No,
> in ANSI X3.279-1996, "AT Attachment Interface with Extensions (ATA-2)",
> Approved September 11, 1996 , control register bit 3-7 are reserved.
>
> However ANSI X3.221-1994, "AT Attachment Interface for Disk Drives",
> Approved May 12, 1994, bit3 is "1" and bits 4-7 are "x". No further explanation.
>
> How far back must we go, to get the sense ?
>
> >
> > This is the drive->ctrl register pointer.
> >
> > outp(drive->ctl|0x02, IDE_CONTROL_REG);
> >
> > typedef union {
> > unsigned all: 8;/* all of the bits together */
> > struct {
> > unsigned bit0 : 1;
> > unsigned nIEN : 1;/* device INTRQ to host */
> > unsigned SRST : 1;/* host soft reset bit */
> > unsigned bit3 : 1;/* ATA-2 thingy */
> > unsigned reserved456: 3;
> > unsigned HOB: 1;/* 48-bit address ordering */
> > } b;
> > } control_t;
> >
> > This is a new struct that is to be added for 48-bit addressing and it will
> > reflect drive->ctl soon. I have not decided how to use it best or at all,
> > but it has meaning and once I add-in the real def of bit3 then I will not
> > need to look it up again.
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Patch(2.4.5): Fix PCMCIA ATA/IDE freeze (w/ PCI add-in cards)V3
Okay my bad it is ATA-1 but even that does not explain the bit.
only that section 7.2.6 top of page 14 (index numbers) defines it to be
set to 1 with out a reason.
This this is a pre-ATA thing back in IDE.
If you really want to know the answer I can go dig it up, but later.
Cheers,
Andre Hedrick
ASL Kernel Development
Linux ATA Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035Web: www.aslab.com
On Fri, 29 Jun 2001, Gunther Mayer wrote:
Andre Hedrick wrote:
That is a legacy bit from ATA-2 but it is one of those things you can not
get rid of :-( even thou things are obsoleted, they are not retired.
This means that you have to go back into the past to see how it was used,
silly! I hope you agree to that point.
No,
in ANSI X3.279-1996, AT Attachment Interface with Extensions (ATA-2),
Approved September 11, 1996 , control register bit 3-7 are reserved.
However ANSI X3.221-1994, AT Attachment Interface for Disk Drives,
Approved May 12, 1994, bit3 is 1 and bits 4-7 are x. No further explanation.
How far back must we go, to get the sense ?
This is the drive-ctrl register pointer.
outp(drive-ctl|0x02, IDE_CONTROL_REG);
typedef union {
unsigned all: 8;/* all of the bits together */
struct {
unsigned bit0 : 1;
unsigned nIEN : 1;/* device INTRQ to host */
unsigned SRST : 1;/* host soft reset bit */
unsigned bit3 : 1;/* ATA-2 thingy */
unsigned reserved456: 3;
unsigned HOB: 1;/* 48-bit address ordering */
} b;
} control_t;
This is a new struct that is to be added for 48-bit addressing and it will
reflect drive-ctl soon. I have not decided how to use it best or at all,
but it has meaning and once I add-in the real def of bit3 then I will not
need to look it up again.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Patch(2.4.5): Fix PCMCIA ATA/IDE freeze (w/ PCI add-in cards)V3
I should have known that you (instructor of the current and previous
maintainer) would have the answer off the top ;-)
Therefore by your description it mys be set always but I guess it is a
DGD; however, I do want to know that it is now.
Oh, and now that Big Drive Technology has been annouced I should finally
send you the code for 48-bit, sorry about the delay.
Cheers,
Andre Hedrick
ASL Kernel Development
Linux ATA Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035Web: www.aslab.com
On Fri, 29 Jun 2001 [EMAIL PROTECTED] wrote:
Andre Hedrick wrote:
That is a legacy bit from ATA-2 but it is one of those things you cannot
get rid of :-(
in ANSI X3.279-1996, AT Attachment Interface with Extensions (ATA-2),
Approved September 11, 1996 , control register bit 3-7 are reserved.
However ANSI X3.221-1994, AT Attachment Interface for Disk Drives,
Approved May 12, 1994, bit3 is 1 and bits 4-7 are x.
No further explanation.
How far back must we go, to get the sense ?
struct {
unsigned bit0 : 1;
unsigned nIEN : 1;/* device INTRQ to host */
unsigned SRST : 1;/* host soft reset bit */
unsigned bit3 : 1;/* ATA-2 thingy */
unsigned reserved456: 3;
unsigned HOB: 1;/* 48-bit address ordering */
} control_t;
once I add-in the real def of bit3 then I will not
need to look it up again.
bit3: 0: drive has 1-8 heads
1: drive has more than 8 heads
(From old MFM/RLL times. In ATA-1 bit3 is set to 1.
See also
http://www.win.tue.nl/~aeb/linux/hdtypes/hdtypes-2.html
.)
Andries
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Patch(2.4.5): Fix PCMCIA ATA/IDE freeze (w/ PCI add-in cards)V3
That is a legacy bit from ATA-2 but it is one of those things you can not
get rid of :-( even thou things are obsoleted, they are not retired.
This means that you have to go back into the past to see how it was used,
silly! I hope you agree to that point.
This is the drive->ctrl register pointer.
outp(drive->ctl|0x02, IDE_CONTROL_REG);
typedef union {
unsigned all: 8;/* all of the bits together */
struct {
unsigned bit0 : 1;
unsigned nIEN : 1;/* device INTRQ to host */
unsigned SRST : 1;/* host soft reset bit */
unsigned bit3 : 1;/* ATA-2 thingy */
unsigned reserved456: 3;
unsigned HOB: 1;/* 48-bit address ordering */
} b;
} control_t;
This is a new struct that is to be added for 48-bit addressing and it will
reflect drive->ctl soon. I have not decided how to use it best or at all,
but it has meaning and once I add-in the real def of bit3 then I will not
need to look it up again.
Cheers,
Andre Hedrick
ASL Kernel Development
Linux ATA Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035Web: www.aslab.com
On Thu, 28 Jun 2001, Gunther Mayer wrote:
> Andre Hedrick wrote:
> >
> > It fixes a BUG in CFA, but what will it do to the other stuff?
> > Parse it exclusive to CFA and there is not an issue.
> ...
> > Not all ./arch have a control register doing this randomly without know the
> > rest of the driver will kill more than it fixes.
> >
>
> Thanks for pointing out this implementation bug. Although I fixed another problem
> in ide-cs, where ctl_base could eventually be 0.
>
> I would rather not add a special hwif->is_pcmcia flag, as
> the control register (if it exists) is well defined
> (bit2=softreset bit1=nIEN, others reserved; however there is
> a hardcoded value of 0x08 somewhere in the ide code?).
>
> -
> Gunther
>
>
>
> --- linux245.orig/drivers/ide/ide-cs.c Fri Feb 9 20:40:02 2001
> +++ linux/drivers/ide/ide-cs.c Thu Jun 28 18:04:27 2001
> @@ -42,6 +42,7 @@
> #include
> #include
> #include
> +#include
>
> #include
> #include
> @@ -223,6 +224,15 @@
> #define CFG_CHECK(fn, args...) \
> if (CardServices(fn, args) != 0) goto next_entry
>
> +int idecs_register (int arg1, int arg2, int irq)
> +{
> +hw_regs_t hw;
> +ide_init_hwif_ports(, (ide_ioreg_t) arg1, (ide_ioreg_t) arg2, NULL);
> +hw.irq = irq;
> +hw.chipset = ide_pci; // this enables IRQ sharing w/ PCI irqs
> +return ide_register_hw(, NULL);
> +}
> +
> void ide_config(dev_link_t *link)
> {
> client_handle_t handle = link->handle;
> @@ -326,10 +336,12 @@
>
> /* retry registration in case device is still spinning up */
> for (i = 0; i < 10; i++) {
> - hd = ide_register(io_base, ctl_base, link->irq.AssignedIRQ);
> + if(ctl_base) outb(0x02, ctl_base); // Set nIEN = disable device interrupts
> + hd = idecs_register(io_base, ctl_base, link->irq.AssignedIRQ);
> if (hd >= 0) break;
> if (link->io.NumPorts1 == 0x20) {
> - hd = ide_register(io_base+0x10, ctl_base+0x10,
> + if(ctl_base) outb(0x02, ctl_base+0x10);
> + hd = idecs_register(io_base+0x10, ctl_base+0x10,
> link->irq.AssignedIRQ);
> if (hd >= 0) {
> io_base += 0x10; ctl_base += 0x10;
> --- linux245.orig/drivers/ide/ide-probe.c Sun Mar 18 18:25:02 2001
> +++ linux/drivers/ide/ide-probe.c Thu Jun 28 18:43:43 2001
> @@ -685,6 +685,9 @@
> #else /* !CONFIG_IDEPCI_SHARE_IRQ */
> int sa = (hwif->chipset == ide_pci) ? SA_INTERRUPT|SA_SHIRQ :
>SA_INTERRUPT;
> #endif /* CONFIG_IDEPCI_SHARE_IRQ */
> +
> + if(hwif->io_ports[IDE_CONTROL_OFFSET])
> + OUT_BYTE(0x00, hwif->io_ports[IDE_CONTROL_OFFSET]); // clear
>nIEN == enable irqs
> if (ide_request_irq(hwif->irq, _intr, sa, hwif->name, hwgroup)) {
> if (!match)
> kfree(hwgroup);
> --- linux245.orig/drivers/ide/ide.c Wed May 2 01:05:00 2001
> +++ linux/drivers/ide/ide.c Thu Jun 28 18:04:42 2001
> @@ -2181,6 +2181,7 @@
> memcpy(hwif->io_ports, hwif->hw.io_ports, sizeof(hwif->hw.io_ports));
> hwif->irq = hw->irq;
> hwif->
Re: Patch(2.4.5): Fix PCMCIA ATA/IDE freeze (w/ PCI add-in cards)V3
That is a legacy bit from ATA-2 but it is one of those things you can not
get rid of :-( even thou things are obsoleted, they are not retired.
This means that you have to go back into the past to see how it was used,
silly! I hope you agree to that point.
This is the drive-ctrl register pointer.
outp(drive-ctl|0x02, IDE_CONTROL_REG);
typedef union {
unsigned all: 8;/* all of the bits together */
struct {
unsigned bit0 : 1;
unsigned nIEN : 1;/* device INTRQ to host */
unsigned SRST : 1;/* host soft reset bit */
unsigned bit3 : 1;/* ATA-2 thingy */
unsigned reserved456: 3;
unsigned HOB: 1;/* 48-bit address ordering */
} b;
} control_t;
This is a new struct that is to be added for 48-bit addressing and it will
reflect drive-ctl soon. I have not decided how to use it best or at all,
but it has meaning and once I add-in the real def of bit3 then I will not
need to look it up again.
Cheers,
Andre Hedrick
ASL Kernel Development
Linux ATA Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035Web: www.aslab.com
On Thu, 28 Jun 2001, Gunther Mayer wrote:
Andre Hedrick wrote:
It fixes a BUG in CFA, but what will it do to the other stuff?
Parse it exclusive to CFA and there is not an issue.
...
Not all ./arch have a control register doing this randomly without know the
rest of the driver will kill more than it fixes.
Thanks for pointing out this implementation bug. Although I fixed another problem
in ide-cs, where ctl_base could eventually be 0.
I would rather not add a special hwif-is_pcmcia flag, as
the control register (if it exists) is well defined
(bit2=softreset bit1=nIEN, others reserved; however there is
a hardcoded value of 0x08 somewhere in the ide code?).
-
Gunther
--- linux245.orig/drivers/ide/ide-cs.c Fri Feb 9 20:40:02 2001
+++ linux/drivers/ide/ide-cs.c Thu Jun 28 18:04:27 2001
@@ -42,6 +42,7 @@
#include linux/ioport.h
#include linux/hdreg.h
#include linux/major.h
+#include linux/ide.h
#include asm/io.h
#include asm/system.h
@@ -223,6 +224,15 @@
#define CFG_CHECK(fn, args...) \
if (CardServices(fn, args) != 0) goto next_entry
+int idecs_register (int arg1, int arg2, int irq)
+{
+hw_regs_t hw;
+ide_init_hwif_ports(hw, (ide_ioreg_t) arg1, (ide_ioreg_t) arg2, NULL);
+hw.irq = irq;
+hw.chipset = ide_pci; // this enables IRQ sharing w/ PCI irqs
+return ide_register_hw(hw, NULL);
+}
+
void ide_config(dev_link_t *link)
{
client_handle_t handle = link-handle;
@@ -326,10 +336,12 @@
/* retry registration in case device is still spinning up */
for (i = 0; i 10; i++) {
- hd = ide_register(io_base, ctl_base, link-irq.AssignedIRQ);
+ if(ctl_base) outb(0x02, ctl_base); // Set nIEN = disable device interrupts
+ hd = idecs_register(io_base, ctl_base, link-irq.AssignedIRQ);
if (hd = 0) break;
if (link-io.NumPorts1 == 0x20) {
- hd = ide_register(io_base+0x10, ctl_base+0x10,
+ if(ctl_base) outb(0x02, ctl_base+0x10);
+ hd = idecs_register(io_base+0x10, ctl_base+0x10,
link-irq.AssignedIRQ);
if (hd = 0) {
io_base += 0x10; ctl_base += 0x10;
--- linux245.orig/drivers/ide/ide-probe.c Sun Mar 18 18:25:02 2001
+++ linux/drivers/ide/ide-probe.c Thu Jun 28 18:43:43 2001
@@ -685,6 +685,9 @@
#else /* !CONFIG_IDEPCI_SHARE_IRQ */
int sa = (hwif-chipset == ide_pci) ? SA_INTERRUPT|SA_SHIRQ :
SA_INTERRUPT;
#endif /* CONFIG_IDEPCI_SHARE_IRQ */
+
+ if(hwif-io_ports[IDE_CONTROL_OFFSET])
+ OUT_BYTE(0x00, hwif-io_ports[IDE_CONTROL_OFFSET]); // clear
nIEN == enable irqs
if (ide_request_irq(hwif-irq, ide_intr, sa, hwif-name, hwgroup)) {
if (!match)
kfree(hwgroup);
--- linux245.orig/drivers/ide/ide.c Wed May 2 01:05:00 2001
+++ linux/drivers/ide/ide.c Thu Jun 28 18:04:42 2001
@@ -2181,6 +2181,7 @@
memcpy(hwif-io_ports, hwif-hw.io_ports, sizeof(hwif-hw.io_ports));
hwif-irq = hw-irq;
hwif-noprobe = 0;
+ hwif-chipset = hw-chipset;
if (!initializing) {
ide_probe_module();
--- linux245.orig/include/linux/ide.h Sat May 26 03:02:42 2001
+++ linux/include/linux/ide.h Thu Jun 28 18:18:05 2001
@@ -226,6 +226,19 @@
#endif
/*
+ * hwif_chipset_t is used to keep track of the specific hardware
+ * chipset used
Re: Patch(2.4.5): Fix PCMCIA ATA/IDE freeze (w/ PCI add-in cards)
On Thu, 28 Jun 2001 [EMAIL PROTECTED] wrote: > From: Andre Hedrick <[EMAIL PROTECTED]> > > You know yourself first and all the screwed up ATAPI products that are > still using SFF-8020 that has been obsoleted before I start maintaining > the subsystem three plus years ago. > > Hi Andre - > > Why precisely is complying to SFF-8020 broken? > That was the standard. The standard that Microsoft required. You have stated it clearly it is past tense. > Other people made a different standard, and claimed that theirs > was better or more official or whatever, but reality is that > the products were not manufactured following this so-called > better standard. Ignoring "junk hardware" is not practical it will bite you everyday all day long.Best example is VIA. > You are a good disciple of Hale, but it is no use ignoring the If one is going to learn the rules it is best to have learned from on of the "Fathers of ATA", and given that I have been crowned "Hale Jr." I take this a compliment. The reality is that I am not anywhere in the same class of understanding as Hale Landis, but getting there. > fact that a very large number of devices was made following SFF-8020. > These devices are not necessarily screwed, they tend to work fine, > although both ATA and ATAPI devices have their quirks. If they all did the same thing (regardless of class) it would be a different issue. Basic things like asking for N amounts of data and getting back N+M > N the buffer allocated. Or worse is the under data-run. Other issues are DRQ, failure to hold/set busy-bit. The ATAPI people do not even follow the rules in the defunct guide. > SFF-8020, later INF-8020, became part of ATA/ATAPI-4 (1998). > The T13 people that merged SFF-8020 and produced ATA/ATAPI-4 > changed a few details about how a master is supposed to react > when a nonexistent slave is selected. Nobody really noticed, That point is only important during POST and execution of drive diagnostics command and Linux does not call that command. > and ATA/ATAPI-5 still had the same requirements. But then long > discussions about this difference caused ATA/ATAPI-6 to go back > to the original SFF-8020 requirements. Do you disagree with this > description of history? If you agree then it is not SFF-8020 > but ATA/ATAPI-4 and ATA/ATAPI-5 that today must be considered broken > in this respect. I am referring to Section 9.16.1 of these standards. > > Maybe there are other things in SFF-8020 that you consider broken? See above, regardless of the brokeness whe have to mucky with it. So I move to develop to a standard that I have influence and direction control, then deal with the exceptions. ATA-X created the "packet-command" and "data-phase-handlers" based on the zero-bit in the error_feature task-register. Lastly it does not exist anymore, a real problem for manufacturers building product on a document that does not exist. Worse is that there are companies making hardware based on SFF-8020 v2.5! Cheers, Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com Expired SFF-8020i Rev 2.6 SFF Committee documentation may be purchased (see p4). SFF Committee documents are available by FaxAccess at 408-741-1600 SFF Committee SFF-8020i Specification for ATA Packet Interface for CD-ROM Rev 2.6 January 22, 1996 Secretariat: SFF Committee Abstract: INF-8020i defines defines a Packet Interface for use with CD-ROM drives that use the ATA (AT Attachment) interface. The members voted in September 1999 that this specification Expire. SFF-8020 has been incorporated into two national standards, SCSI MMC (Multi Media Commands) and ATA/ATAPI (AT Attachment). For current information, see: - www.t10.org for the latest revision of SCSI MMC-x - www.t13.org for the latest revision of ATA/ATAPI-x
Re: Patch(2.4.5): Fix PCMCIA ATA/IDE freeze (w/ PCI add-in cards)
Gunther,
It fixes a BUG in CFA, but what will it do to the other stuff?
Parse it exclusive to CFA and there is not an issue.
Also look closely
No all ./arch have a control register doing this randomly without know the
rest of the driver will kill more than it fixes.
static int try_to_identify (ide_drive_t *drive, byte cmd)
{
int rc;
ide_ioreg_t hd_status;
unsigned long timeout;
unsigned long irqs = 0;
byte s, a;
if (IDE_CONTROL_REG) {
} else {
ide_delay_50ms();
hd_status = IDE_STATUS_REG;
}
}
It will not be accepted until it correctly address and handles all HOSTs
correctly, period.
Andre Hedrick
ASL Kernel Development
Linux ATA Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035Web: www.aslab.com
On Wed, 27 Jun 2001, Gunther Mayer wrote:
> Andre Hedrick wrote:
> >
> > PARANIOA.
>
> This is not a valid reason.
>
> This clearly fixes a bug in linux. Note: the irq disable
> is local to ide-cs. Are you paranoid enough to believe
> enabling the irq by writing globally to the control register that
> existed since ATA will have ill effects?
>
> You claim the relevant PCMCIA ATA behaviour is not ATA(>3?) compliant,
> however you didn`t yet give any facts to support this !
>
> You claim this locks the driver, again no facts.
>
>
> >
> > Remember that ATAPI is generally screwed beyond reality, so adjusting the
> > probe code in general (global) is a bad thing.
> ...
> > On Wed, 27 Jun 2001, Alan Cox wrote:
> >
> > > > obsoleting ATA-2 did their attention at CFA become alarmed. I agree that
> > > > there needs to be a fix, but not at the price of locking the rest of the
> > > > driver. Since we now the identity of the device prior to assigned the
> > > > interrupt we can handle the execption, but you do not go around blanket
> > > > wacking the control register of all devices.
>
> The proposed patch is very simple (as per Linus' liking). When considering to
> install an earlier (and global) irq handler I believe you can see
> this will impose a much greater risk !
>
> > >
> > > I dont see why it locks up the driver ?
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Patch(2.4.5): Fix PCMCIA ATA/IDE freeze (w/ PCI add-in cards)
PARANIOA. Remember that ATAPI is generally screwed beyond reality, so adjusting the probe code in general (global) is a bad thing. Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com On Wed, 27 Jun 2001, Alan Cox wrote: > > obsoleting ATA-2 did their attention at CFA become alarmed. I agree that > > there needs to be a fix, but not at the price of locking the rest of the > > driver. Since we now the identity of the device prior to assigned the > > interrupt we can handle the execption, but you do not go around blanket > > wacking the control register of all devices. > > I dont see why it locks up the driver ? > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Patch(2.4.5): Fix PCMCIA ATA/IDE freeze (w/ PCI add-in cards)
It should be all devices that do not claim ATA-4/5 support. I have to go back and look to see what the cut-off was that CFA agreed to move forward off the dead docs. Cheers, Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com On Wed, 27 Jun 2001, David Hinds wrote: > On Wed, Jun 27, 2001 at 12:29:47AM -0700, Andre Hedrick wrote: > > > > I can not help if you have a device that not compliant to the rules. > > ATA-2 is OBSOLETED thus we forced (the NCITS Standards Body) the CFA > > people to move to ATA-4 or ATA-5. > > > > That device is enabling with its ablity to assert its device->host > > interrupt regardless of the HOST...that is a bad device. > > > > Send me the manufacturer and I will tear them apart for making a > > non-compliant device. Then figure out a way to de-assert the like > > regardless if it exists without hang the rest of the driver. > > I don't understand the ATA spec issue, but *every* PCMCIA ATA device I > know of (including all SmartMedia, CompactFlash, etc) suffers from > this problem. It is not an isolated manufacturer. As far as I know, > the IDE driver has always had the problem that it may trigger > interrupts before it installs a handler. Are you saying that is only > true of pre-ATA-4 devices, or only devices that deviate from the spec? > > -- Dave > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Patch(2.4.5): Fix PCMCIA ATA/IDE freeze (w/ PCI add-in cards)
Alan, It is an issue that we have been trying to get fixed, and only after obsoleting ATA-2 did their attention at CFA become alarmed. I agree that there needs to be a fix, but not at the price of locking the rest of the driver. Since we now the identity of the device prior to assigned the interrupt we can handle the execption, but you do not go around blanket wacking the control register of all devices. You know yourself first and all the screwed up ATAPI products that are still using SFF-8020 that has been obsoleted before I start maintaining the subsystem three plus years ago. The only way to get hardware fixed is to point out is broken and force the issue. I have one of these broken device with me, but I quit using it because of that hardware flaw, mostly because I did not have the time to deal with CFA and there lameness to follow the rules even when huge amounts of time have passed between the notification and execution of obsolesense (sp). Since David claims it is a known error we need to take the dirty list in ide.c dealing with CFA's that are detected by name strings or correctly putting in the CFA signature in word0 of identify. I have no problem in fixing it, just blanket chopper gunning is not always safe. Cheers, Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com On Wed, 27 Jun 2001, Alan Cox wrote: > > I can not help if you have a device that not compliant to the rules. > > ATA-2 is OBSOLETED thus we forced (the NCITS Standards Body) the CFA > > ATA-2 may be obsolete but existing ATA-2 hardware doesnt spontaenously > combust when the spec changes (much Im sure to some vendors dissappointmnent) > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Patch(2.4.5): Fix PCMCIA ATA/IDE freeze (w/ PCI add-in cards)
I can not help if you have a device that not compliant to the rules.
ATA-2 is OBSOLETED thus we forced (the NCITS Standards Body) the CFA
people to move to ATA-4 or ATA-5.
That device is enabling with its ablity to assert its device->host
interrupt regardless of the HOST...that is a bad device.
Send me the manufacturer and I will tear them apart for making a
non-compliant device. Then figure out a way to de-assert the like
regardless if it exists without hang the rest of the driver.
Cheers,
On Tue, 26 Jun 2001, Gunther Mayer wrote:
> Hi,
>
> this patch fixes the hard hang (no SYSRQ) on inserting
> any PCMCIA ATA/IDE card (e.g. CompactFlash, Clik40 etc)
> to a PCI-Cardbus bridge add-in card.
>
> Thanks David for his valuable explanation about what happens:
> ide-probe registers it's irq handler too late! After it
> triggers the interrupt during the probe the (shared) irq
> loops forever, effectively wedging the machine completely.
>
> Regards, Gunther
>
>
>
> --- linux245.orig/drivers/ide/ide-cs.c Fri Feb 9 20:40:02 2001
> +++ linux/drivers/ide/ide-cs.c Tue Jun 26 21:22:19 2001
> @@ -324,6 +324,9 @@
> if (link->io.NumPorts2)
> release_region(link->io.BasePort2, link->io.NumPorts2);
>
> +outb(0x02, ctl_base); // Set nIEN = disable device interrupts
> + // else it hangs on PCI-Cardbus add-in cards, wedging irq
> +
> /* retry registration in case device is still spinning up */
> for (i = 0; i < 10; i++) {
> hd = ide_register(io_base, ctl_base, link->irq.AssignedIRQ);
> --- linux245.orig/drivers/ide/ide-probe.c Sun Mar 18 18:25:02 2001
> +++ linux/drivers/ide/ide-probe.c Tue Jun 26 21:25:07 2001
> @@ -685,6 +685,8 @@
> #else /* !CONFIG_IDEPCI_SHARE_IRQ */
> int sa = (hwif->chipset == ide_pci) ? SA_INTERRUPT|SA_SHIRQ :
>SA_INTERRUPT;
> #endif /* CONFIG_IDEPCI_SHARE_IRQ */
> +
> + outb(0x00, hwif->io_ports[IDE_CONTROL_OFFSET]); // clear nIEN ==
>enable irqs
> if (ide_request_irq(hwif->irq, _intr, sa, hwif->name, hwgroup)) {
> if (!match)
> kfree(hwgroup);
>
Andre Hedrick
ASL Kernel Development
Linux ATA Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035Web: www.aslab.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Patch(2.4.5): Fix PCMCIA ATA/IDE freeze (w/ PCI add-in cards)
I can not help if you have a device that not compliant to the rules.
ATA-2 is OBSOLETED thus we forced (the NCITS Standards Body) the CFA
people to move to ATA-4 or ATA-5.
That device is enabling with its ablity to assert its device-host
interrupt regardless of the HOST...that is a bad device.
Send me the manufacturer and I will tear them apart for making a
non-compliant device. Then figure out a way to de-assert the like
regardless if it exists without hang the rest of the driver.
Cheers,
On Tue, 26 Jun 2001, Gunther Mayer wrote:
Hi,
this patch fixes the hard hang (no SYSRQ) on inserting
any PCMCIA ATA/IDE card (e.g. CompactFlash, Clik40 etc)
to a PCI-Cardbus bridge add-in card.
Thanks David for his valuable explanation about what happens:
ide-probe registers it's irq handler too late! After it
triggers the interrupt during the probe the (shared) irq
loops forever, effectively wedging the machine completely.
Regards, Gunther
--- linux245.orig/drivers/ide/ide-cs.c Fri Feb 9 20:40:02 2001
+++ linux/drivers/ide/ide-cs.c Tue Jun 26 21:22:19 2001
@@ -324,6 +324,9 @@
if (link-io.NumPorts2)
release_region(link-io.BasePort2, link-io.NumPorts2);
+outb(0x02, ctl_base); // Set nIEN = disable device interrupts
+ // else it hangs on PCI-Cardbus add-in cards, wedging irq
+
/* retry registration in case device is still spinning up */
for (i = 0; i 10; i++) {
hd = ide_register(io_base, ctl_base, link-irq.AssignedIRQ);
--- linux245.orig/drivers/ide/ide-probe.c Sun Mar 18 18:25:02 2001
+++ linux/drivers/ide/ide-probe.c Tue Jun 26 21:25:07 2001
@@ -685,6 +685,8 @@
#else /* !CONFIG_IDEPCI_SHARE_IRQ */
int sa = (hwif-chipset == ide_pci) ? SA_INTERRUPT|SA_SHIRQ :
SA_INTERRUPT;
#endif /* CONFIG_IDEPCI_SHARE_IRQ */
+
+ outb(0x00, hwif-io_ports[IDE_CONTROL_OFFSET]); // clear nIEN ==
enable irqs
if (ide_request_irq(hwif-irq, ide_intr, sa, hwif-name, hwgroup)) {
if (!match)
kfree(hwgroup);
Andre Hedrick
ASL Kernel Development
Linux ATA Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035Web: www.aslab.com
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Patch(2.4.5): Fix PCMCIA ATA/IDE freeze (w/ PCI add-in cards)
It should be all devices that do not claim ATA-4/5 support. I have to go back and look to see what the cut-off was that CFA agreed to move forward off the dead docs. Cheers, Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com On Wed, 27 Jun 2001, David Hinds wrote: On Wed, Jun 27, 2001 at 12:29:47AM -0700, Andre Hedrick wrote: I can not help if you have a device that not compliant to the rules. ATA-2 is OBSOLETED thus we forced (the NCITS Standards Body) the CFA people to move to ATA-4 or ATA-5. That device is enabling with its ablity to assert its device-host interrupt regardless of the HOST...that is a bad device. Send me the manufacturer and I will tear them apart for making a non-compliant device. Then figure out a way to de-assert the like regardless if it exists without hang the rest of the driver. I don't understand the ATA spec issue, but *every* PCMCIA ATA device I know of (including all SmartMedia, CompactFlash, etc) suffers from this problem. It is not an isolated manufacturer. As far as I know, the IDE driver has always had the problem that it may trigger interrupts before it installs a handler. Are you saying that is only true of pre-ATA-4 devices, or only devices that deviate from the spec? -- Dave - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Patch(2.4.5): Fix PCMCIA ATA/IDE freeze (w/ PCI add-in cards)
Alan, It is an issue that we have been trying to get fixed, and only after obsoleting ATA-2 did their attention at CFA become alarmed. I agree that there needs to be a fix, but not at the price of locking the rest of the driver. Since we now the identity of the device prior to assigned the interrupt we can handle the execption, but you do not go around blanket wacking the control register of all devices. You know yourself first and all the screwed up ATAPI products that are still using SFF-8020 that has been obsoleted before I start maintaining the subsystem three plus years ago. The only way to get hardware fixed is to point out is broken and force the issue. I have one of these broken device with me, but I quit using it because of that hardware flaw, mostly because I did not have the time to deal with CFA and there lameness to follow the rules even when huge amounts of time have passed between the notification and execution of obsolesense (sp). Since David claims it is a known error we need to take the dirty list in ide.c dealing with CFA's that are detected by name strings or correctly putting in the CFA signature in word0 of identify. I have no problem in fixing it, just blanket chopper gunning is not always safe. Cheers, Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com On Wed, 27 Jun 2001, Alan Cox wrote: I can not help if you have a device that not compliant to the rules. ATA-2 is OBSOLETED thus we forced (the NCITS Standards Body) the CFA ATA-2 may be obsolete but existing ATA-2 hardware doesnt spontaenously combust when the spec changes (much Im sure to some vendors dissappointmnent) - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Patch(2.4.5): Fix PCMCIA ATA/IDE freeze (w/ PCI add-in cards)
PARANIOA. Remember that ATAPI is generally screwed beyond reality, so adjusting the probe code in general (global) is a bad thing. Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com On Wed, 27 Jun 2001, Alan Cox wrote: obsoleting ATA-2 did their attention at CFA become alarmed. I agree that there needs to be a fix, but not at the price of locking the rest of the driver. Since we now the identity of the device prior to assigned the interrupt we can handle the execption, but you do not go around blanket wacking the control register of all devices. I dont see why it locks up the driver ? - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Patch(2.4.5): Fix PCMCIA ATA/IDE freeze (w/ PCI add-in cards)
On Thu, 28 Jun 2001 [EMAIL PROTECTED] wrote: From: Andre Hedrick [EMAIL PROTECTED] You know yourself first and all the screwed up ATAPI products that are still using SFF-8020 that has been obsoleted before I start maintaining the subsystem three plus years ago. Hi Andre - Why precisely is complying to SFF-8020 broken? That was the standard. The standard that Microsoft required. You have stated it clearly it is past tense. Other people made a different standard, and claimed that theirs was better or more official or whatever, but reality is that the products were not manufactured following this so-called better standard. Ignoring junk hardware is not practical it will bite you everyday all day long.Best example is VIA. You are a good disciple of Hale, but it is no use ignoring the If one is going to learn the rules it is best to have learned from on of the Fathers of ATA, and given that I have been crowned Hale Jr. I take this a compliment. The reality is that I am not anywhere in the same class of understanding as Hale Landis, but getting there. fact that a very large number of devices was made following SFF-8020. These devices are not necessarily screwed, they tend to work fine, although both ATA and ATAPI devices have their quirks. If they all did the same thing (regardless of class) it would be a different issue. Basic things like asking for N amounts of data and getting back N+M N the buffer allocated. Or worse is the under data-run. Other issues are DRQ, failure to hold/set busy-bit. The ATAPI people do not even follow the rules in the defunct guide. SFF-8020, later INF-8020, became part of ATA/ATAPI-4 (1998). The T13 people that merged SFF-8020 and produced ATA/ATAPI-4 changed a few details about how a master is supposed to react when a nonexistent slave is selected. Nobody really noticed, That point is only important during POST and execution of drive diagnostics command and Linux does not call that command. and ATA/ATAPI-5 still had the same requirements. But then long discussions about this difference caused ATA/ATAPI-6 to go back to the original SFF-8020 requirements. Do you disagree with this description of history? If you agree then it is not SFF-8020 but ATA/ATAPI-4 and ATA/ATAPI-5 that today must be considered broken in this respect. I am referring to Section 9.16.1 of these standards. Maybe there are other things in SFF-8020 that you consider broken? See above, regardless of the brokeness whe have to mucky with it. So I move to develop to a standard that I have influence and direction control, then deal with the exceptions. ATA-X created the packet-command and data-phase-handlers based on the zero-bit in the error_feature task-register. Lastly it does not exist anymore, a real problem for manufacturers building product on a document that does not exist. Worse is that there are companies making hardware based on SFF-8020 v2.5! Cheers, Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com Expired SFF-8020i Rev 2.6 SFF Committee documentation may be purchased (see p4). SFF Committee documents are available by FaxAccess at 408-741-1600 SFF Committee SFF-8020i Specification for ATA Packet Interface for CD-ROM Rev 2.6 January 22, 1996 Secretariat: SFF Committee Abstract: INF-8020i defines defines a Packet Interface for use with CD-ROM drives that use the ATA (AT Attachment) interface. The members voted in September 1999 that this specification Expire. SFF-8020 has been incorporated into two national standards, SCSI MMC (Multi Media Commands) and ATA/ATAPI (AT Attachment). For current information, see: - www.t10.org for the latest revision of SCSI MMC-x - www.t13.org for the latest revision of ATA/ATAPI-x
Re: Patch(2.4.5): Fix PCMCIA ATA/IDE freeze (w/ PCI add-in cards)
Gunther,
It fixes a BUG in CFA, but what will it do to the other stuff?
Parse it exclusive to CFA and there is not an issue.
Also look closely
No all ./arch have a control register doing this randomly without know the
rest of the driver will kill more than it fixes.
static int try_to_identify (ide_drive_t *drive, byte cmd)
{
int rc;
ide_ioreg_t hd_status;
unsigned long timeout;
unsigned long irqs = 0;
byte s, a;
if (IDE_CONTROL_REG) {
snip
} else {
ide_delay_50ms();
hd_status = IDE_STATUS_REG;
}
snip
}
It will not be accepted until it correctly address and handles all HOSTs
correctly, period.
Andre Hedrick
ASL Kernel Development
Linux ATA Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035Web: www.aslab.com
On Wed, 27 Jun 2001, Gunther Mayer wrote:
Andre Hedrick wrote:
PARANIOA.
This is not a valid reason.
This clearly fixes a bug in linux. Note: the irq disable
is local to ide-cs. Are you paranoid enough to believe
enabling the irq by writing globally to the control register that
existed since ATA will have ill effects?
You claim the relevant PCMCIA ATA behaviour is not ATA(3?) compliant,
however you didn`t yet give any facts to support this !
You claim this locks the driver, again no facts.
Remember that ATAPI is generally screwed beyond reality, so adjusting the
probe code in general (global) is a bad thing.
...
On Wed, 27 Jun 2001, Alan Cox wrote:
obsoleting ATA-2 did their attention at CFA become alarmed. I agree that
there needs to be a fix, but not at the price of locking the rest of the
driver. Since we now the identity of the device prior to assigned the
interrupt we can handle the execption, but you do not go around blanket
wacking the control register of all devices.
The proposed patch is very simple (as per Linus' liking). When considering to
install an earlier (and global) irq handler I believe you can see
this will impose a much greater risk !
I dont see why it locks up the driver ?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Eye2Eye a hope for Promise to Join Linux
Greetings Craig, I would like to publicly thank you for coming to the table of GNU/GPL with an open perspective. After 90 minutes on the phone, of which 45 minutes were me pointing out issues promblems and complaints w/ 20 minutes on ways to work on solutions in the near and distant future and the listening to your concerns and questions between my moments of interruption. The next conversion will not have the burst-in moments because it will be in person or my cell battery will be fully charged. Since you have stated "I will not make promise, I can not keep" this is a good thing and it will go a fair way to clean up messes from the past on both sides. I look forward to Promise working with Linux in meaningful and productive ways. Please reply and correct anything that is mistated by me or verify the correctness. This will show an action of good-faith before all those watching here. Respectfully, Andre Hedrick Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [craigl@promise.com: Getting A Patch Into The Kernel] (fwd)
nd he was new to this, woudn't it be a nice first > impression to clearly say "this licensing issue is blocking the inclusion of > your code" so he knows what the problem is rather than "we're biased against > promise, so we're going to pick on you and call you names?" > > > Mind you that at one point I had two people in the San Jose > > office that were friendly be they are now gone. > > If you've approached every new person from promise this way ever since, I'm > not exactly suprised you haven't met more like them. (I honestly hope that > the previous sentence was a harsh and unfair assessment, and that you haven't > been doing that.) It is unfair, because I got screwed by Promise just this past April. It was the last time and I told them that fact. > No corporation is truly a monolithic entity. It's just a bunch of disjointed > individuals who spend a lot of time in meetings filling out forms. You can > deal with them as a faceless professional with a known set of duties, or you > can try to deal with them as a human being. In this case you are wrong and I wish you were not. Lastly, I gave this fellow my mobile cell-number and told him that I do not want his driver, I want honesty and that I am mad and tired of the story-line and "Broken Promise's" that they send and sell. So Craig, my phone has not rung or your story has not changed. Regards, Andre Hedrick Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [craigl@promise.com: Getting A Patch Into The Kernel] (fwd)
No I would not take their code and apply it. I might not even want to look at it. All I want is the API rules to the signatures and we have them now. We do not need their driver. Next insults to linux in this form are unacceptable means of communication. * This support will also include a version of our FastCheck utility for X-Windows. To start we will only support distribution versions of the kernel. No test or beta kernels will be supported at this time. Promise realizes that support could have come much sooner but as I started earlier we are much more concerned with compatibility and quality rather than rushing support to the market at the expense of the end user. Hopefully this answers you immediate questions about our Linux support structure. * Stating/Implying that Linux Maintainers do not care about "quality". Oh it gets much worse, but I want to see if the sales for Promise have hit hard enough to break their linux-unfriendly additude. Mind you the came begging for help because their sales are off, and I was willing to help on the terms of GPL/GNU and mine. But GPL/GNU was to big to choke down. When the sales hurt enough and they have not choice, I will reconsider. Breathe, because you die before I change my position, if you are hold a breath. I do not trust Promise, and three years of their general arrogance is more than enough. Mind you that at one point I had two people in the San Jose office that were friendly be they are now gone. They got to close to GPL/GNU and something happened. Regards, Andre Hedrick Linux ATA Development On Wed, 13 Jun 2001, bert hubert wrote: > On Tue, Jun 12, 2001 at 11:22:56PM -0700, Andre Hedrick wrote: > > > I do not want or need your company's patches, period. > > That's just not true and you know it. If the patches were to be written in > cooperation with you and of proper quality and license you would love them. > > > I will not take or accept or approve of any dirty code that allows the a > > poorly written binary driver that can not control its ISR and it > > interferes irresponsiblily with the native ATA driver. > > That's the real issue of course. Craig contacted you to find out what was > wrong and you should explain to him what the problems are, and how he could > solve them. Linus would accept patches written by Bill Gates if they were > licensed right and coded properly, so I don't see why Promise should be an > exception. > > Never get angry at bad code. Only explain people why it's bad. At length if > needed. > > Craig: > > > instead each disk is seen individually, and the users data cannot be > > properly accessed. We have a patch that fixes this and are wondering if it > > is possible to get this patch into the kernel, and if so, how this would be > > done? > > The procedure is to publish the patch publically and have people comment and > try it. They will often find that your code is not up to par or does things > in ways that do not please the kernel people. No evil is intended, it is > just that the kernel developers are a choosy bunch. But given the right > prodding they will tell you how you could change your code so that it is > acceptable. Alternatively, people here might see what needs to be done from > your patch, and do it themselves. > > > I apologize if this is the incorrect e-mail to be making this request to. If > > this is not the correct address to be posting this message, any assistance > > as to where it should be directed would be greatly appreciated. > > This was definitely the right email address :-) Mr Hedrick appears not to > like your work and as he is prone to do, he explained so graphically. This > happens. The main thing is to approach kernel coders from a technical > standpoint - they are not interested in commercial pressures or deadlines. > Get your technical people to talk to 'our' technical people and make sure > that they realise that it should be done 'our way' (as it is 'our code') > and things will go swimmingly. > > > http:\\www.promise.com > > Reversing those backslashes might aid your credibility here :-) If you ever > feel that you don't understand these strange linux people, please contact me > or some other people. It can be a weird country, especially coming from a > marketing devision. Thanks for trying! > > But do understand that no amount of prodding, cajoling or legal pressure > will get any company anywhere. That's just not the way. As we say "It's the > code, stupid!". Good luck! > > Regards, > > bert hubert > > > > > - > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > > the body of a message to [EMAIL PROTECTED] > > More majordo
[craigl@promise.com: Getting A Patch Into The Kernel] (fwd)
Mr. Craig Lyons, I do not want or need your company's patches, period. I will not take or accept or approve of any dirty code that allows the a poorly written binary driver that can not control its ISR and it interferes irresponsiblily with the native ATA driver. These are the words from your dear "Linus Chen". Oh answer your voice mail, I left you a message. Regards, Andre Hedrick Linux ATA Development - Forwarded message from Craig Lyons <[EMAIL PROTECTED]> - X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Sender: [EMAIL PROTECTED] Message-ID: <005101c0f38f$e2000960$[EMAIL PROTECTED]> From: "Craig Lyons" <[EMAIL PROTECTED]> Date: Tue, 12 Jun 2001 15:34:43 -0700 To: <[EMAIL PROTECTED]> Subject: Getting A Patch Into The Kernel Importance: Normal Hello, My name is Craig Lyons and I am the marketing manager at Promise Technology. We have a question and are hoping you can point us in the right direction. In the 2.4 kernel there is support for some of our products (Ultra 66, Ultra 100, etc.). As you may or may not know, our Ultra family of controllers (which are just standard IDE controllers and do not have RAID) use the same ASIC on them as our FastTrak RAID controllers do. The 2.4 kernel will recognize our Ultra family of controllers, but there is a problem in that a FastTrak will not be recognized as a FastTrak, but as an Ultra. Consequently, the array on the FastTrak is not recognized as an array, but instead each disk is seen individually, and the users data cannot be properly accessed. We have a patch that fixes this and are wondering if it is possible to get this patch into the kernel, and if so, how this would be done? I apologize if this is the incorrect e-mail to be making this request to. If this is not the correct address to be posting this message, any assistance as to where it should be directed would be greatly appreciated. Regards, Craig Craig Lyons Marketing Manager Promise Technology 1460 Koll Circle San Jose, CA 95112 USA Voice - 408-452-0948 ext. 241 Fax - 408-452-1534 [EMAIL PROTECTED] http:\\www.promise.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[craigl@promise.com: Getting A Patch Into The Kernel] (fwd)
Mr. Craig Lyons, I do not want or need your company's patches, period. I will not take or accept or approve of any dirty code that allows the a poorly written binary driver that can not control its ISR and it interferes irresponsiblily with the native ATA driver. These are the words from your dear Linus Chen. Oh answer your voice mail, I left you a message. Regards, Andre Hedrick Linux ATA Development - Forwarded message from Craig Lyons [EMAIL PROTECTED] - X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) Sender: [EMAIL PROTECTED] Message-ID: 005101c0f38f$e2000960$[EMAIL PROTECTED] From: Craig Lyons [EMAIL PROTECTED] Date: Tue, 12 Jun 2001 15:34:43 -0700 To: [EMAIL PROTECTED] Subject: Getting A Patch Into The Kernel Importance: Normal Hello, My name is Craig Lyons and I am the marketing manager at Promise Technology. We have a question and are hoping you can point us in the right direction. In the 2.4 kernel there is support for some of our products (Ultra 66, Ultra 100, etc.). As you may or may not know, our Ultra family of controllers (which are just standard IDE controllers and do not have RAID) use the same ASIC on them as our FastTrak RAID controllers do. The 2.4 kernel will recognize our Ultra family of controllers, but there is a problem in that a FastTrak will not be recognized as a FastTrak, but as an Ultra. Consequently, the array on the FastTrak is not recognized as an array, but instead each disk is seen individually, and the users data cannot be properly accessed. We have a patch that fixes this and are wondering if it is possible to get this patch into the kernel, and if so, how this would be done? I apologize if this is the incorrect e-mail to be making this request to. If this is not the correct address to be posting this message, any assistance as to where it should be directed would be greatly appreciated. Regards, Craig Craig Lyons Marketing Manager Promise Technology 1460 Koll Circle San Jose, CA 95112 USA Voice - 408-452-0948 ext. 241 Fax - 408-452-1534 [EMAIL PROTECTED] http:\\www.promise.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [craigl@promise.com: Getting A Patch Into The Kernel] (fwd)
No I would not take their code and apply it. I might not even want to look at it. All I want is the API rules to the signatures and we have them now. We do not need their driver. Next insults to linux in this form are unacceptable means of communication. * This support will also include a version of our FastCheck utility for X-Windows. To start we will only support distribution versions of the kernel. No test or beta kernels will be supported at this time. Promise realizes that support could have come much sooner but as I started earlier we are much more concerned with compatibility and quality rather than rushing support to the market at the expense of the end user. Hopefully this answers you immediate questions about our Linux support structure. * Stating/Implying that Linux Maintainers do not care about quality. Oh it gets much worse, but I want to see if the sales for Promise have hit hard enough to break their linux-unfriendly additude. Mind you the came begging for help because their sales are off, and I was willing to help on the terms of GPL/GNU and mine. But GPL/GNU was to big to choke down. When the sales hurt enough and they have not choice, I will reconsider. Breathe, because you die before I change my position, if you are hold a breath. I do not trust Promise, and three years of their general arrogance is more than enough. Mind you that at one point I had two people in the San Jose office that were friendly be they are now gone. They got to close to GPL/GNU and something happened. Regards, Andre Hedrick Linux ATA Development On Wed, 13 Jun 2001, bert hubert wrote: On Tue, Jun 12, 2001 at 11:22:56PM -0700, Andre Hedrick wrote: I do not want or need your company's patches, period. That's just not true and you know it. If the patches were to be written in cooperation with you and of proper quality and license you would love them. I will not take or accept or approve of any dirty code that allows the a poorly written binary driver that can not control its ISR and it interferes irresponsiblily with the native ATA driver. That's the real issue of course. Craig contacted you to find out what was wrong and you should explain to him what the problems are, and how he could solve them. Linus would accept patches written by Bill Gates if they were licensed right and coded properly, so I don't see why Promise should be an exception. Never get angry at bad code. Only explain people why it's bad. At length if needed. Craig: instead each disk is seen individually, and the users data cannot be properly accessed. We have a patch that fixes this and are wondering if it is possible to get this patch into the kernel, and if so, how this would be done? The procedure is to publish the patch publically and have people comment and try it. They will often find that your code is not up to par or does things in ways that do not please the kernel people. No evil is intended, it is just that the kernel developers are a choosy bunch. But given the right prodding they will tell you how you could change your code so that it is acceptable. Alternatively, people here might see what needs to be done from your patch, and do it themselves. I apologize if this is the incorrect e-mail to be making this request to. If this is not the correct address to be posting this message, any assistance as to where it should be directed would be greatly appreciated. This was definitely the right email address :-) Mr Hedrick appears not to like your work and as he is prone to do, he explained so graphically. This happens. The main thing is to approach kernel coders from a technical standpoint - they are not interested in commercial pressures or deadlines. Get your technical people to talk to 'our' technical people and make sure that they realise that it should be done 'our way' (as it is 'our code') and things will go swimmingly. http:\\www.promise.com Reversing those backslashes might aid your credibility here :-) If you ever feel that you don't understand these strange linux people, please contact me or some other people. It can be a weird country, especially coming from a marketing devision. Thanks for trying! But do understand that no amount of prodding, cajoling or legal pressure will get any company anywhere. That's just not the way. As we say It's the code, stupid!. Good luck! Regards, bert hubert - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ -- http
Re: [craigl@promise.com: Getting A Patch Into The Kernel] (fwd)
point I had two people in the San Jose office that were friendly be they are now gone. If you've approached every new person from promise this way ever since, I'm not exactly suprised you haven't met more like them. (I honestly hope that the previous sentence was a harsh and unfair assessment, and that you haven't been doing that.) It is unfair, because I got screwed by Promise just this past April. It was the last time and I told them that fact. No corporation is truly a monolithic entity. It's just a bunch of disjointed individuals who spend a lot of time in meetings filling out forms. You can deal with them as a faceless professional with a known set of duties, or you can try to deal with them as a human being. In this case you are wrong and I wish you were not. Lastly, I gave this fellow my mobile cell-number and told him that I do not want his driver, I want honesty and that I am mad and tired of the story-line and Broken Promise's that they send and sell. So Craig, my phone has not rung or your story has not changed. Regards, Andre Hedrick Linux ATA Development - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Eye2Eye a hope for Promise to Join Linux
Greetings Craig, I would like to publicly thank you for coming to the table of GNU/GPL with an open perspective. After 90 minutes on the phone, of which 45 minutes were me pointing out issues promblems and complaints w/ 20 minutes on ways to work on solutions in the near and distant future and the listening to your concerns and questions between my moments of interruption. The next conversion will not have the burst-in moments because it will be in person or my cell battery will be fully charged. Since you have stated I will not make promise, I can not keep this is a good thing and it will go a fair way to clean up messes from the past on both sides. I look forward to Promise working with Linux in meaningful and productive ways. Please reply and correct anything that is mistated by me or verify the correctness. This will show an action of good-faith before all those watching here. Respectfully, Andre Hedrick Linux ATA Development - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: No DMA with ATAPI devices on PDC20267
On Sun, 10 Jun 2001, Stephen Mollett wrote: > Greetings, > > When using ATAPI devices on a Promise Ultra100 (PDC20267), DMA is not > enabled. Is this a bug in the pdc202xx driver or a limitation of the chipset? > > eg. > With the drive attached to a VIA 82C686: > hdb: ATAPI 40X CD-ROM CD-R/RW drive, 8192kB Cache, UDMA(25) > > With the drive attached to an Ultra100: > hde: ATAPI 40X CD-ROM CD-R/RW drive, 8192kB Cache > > I have also tested this with a DVD-ROM and an LS-120 drive. Hard disks are > fine, however. > > Regards, > Stephen Mollett > Stephen, I can make it do DMA ATAPI, however I have to add the code that used the second DMA engine space. Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: No DMA with ATAPI devices on PDC20267
On Sun, 10 Jun 2001, Stephen Mollett wrote: Greetings, When using ATAPI devices on a Promise Ultra100 (PDC20267), DMA is not enabled. Is this a bug in the pdc202xx driver or a limitation of the chipset? eg. With the drive attached to a VIA 82C686: hdb: ATAPI 40X CD-ROM CD-R/RW drive, 8192kB Cache, UDMA(25) With the drive attached to an Ultra100: hde: ATAPI 40X CD-ROM CD-R/RW drive, 8192kB Cache I have also tested this with a DVD-ROM and an LS-120 drive. Hard disks are fine, however. Regards, Stephen Mollett Stephen, I can make it do DMA ATAPI, however I have to add the code that used the second DMA engine space. Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux support for PDC20268
I am betting on CMD and Highpoint. I will meet with CMD in Irvine during the next T13 meeting in two weeks. Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com On Fri, 8 Jun 2001, Frank Neuber wrote: > Andre Hedrick wrote: > > > > Frank, > > > > "Frank Tiernan" does not exist at Promise anymore, and that company is > > HOSTILE towards Linux Now. > Hi Andre, > thanks for your response. What is your advice for an IDE-Controller > in an multi platform environment? > > Frank > > -- > Dipl.-Ing. Elektrotechnik convergence integrated media gmbh / HW > Frank NeuberRosenthalerstr.51 / 10178 Berlin > Email: [EMAIL PROTECTED] Phone: +49(0)30-72 62 06 50 > WWW:www.convergence.de Fax:+49(0)30-72 62 06 55 > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux support for PDC20268
I am betting on CMD and Highpoint. I will meet with CMD in Irvine during the next T13 meeting in two weeks. Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com On Fri, 8 Jun 2001, Frank Neuber wrote: Andre Hedrick wrote: Frank, Frank Tiernan does not exist at Promise anymore, and that company is HOSTILE towards Linux Now. Hi Andre, thanks for your response. What is your advice for an IDE-Controller in an multi platform environment? Frank -- Dipl.-Ing. Elektrotechnik convergence integrated media gmbh / HW Frank NeuberRosenthalerstr.51 / 10178 Berlin Email: [EMAIL PROTECTED] Phone: +49(0)30-72 62 06 50 WWW:www.convergence.de Fax:+49(0)30-72 62 06 55 - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux support for PDC20268
Frank, "Frank Tiernan" does not exist at Promise anymore, and that company is HOSTILE towards Linux Now. On Tue, 5 Jun 2001, Frank Neuber wrote: > Hi Andre, > I try to set up IDE-Support for ARM-Integrator with an PDC20268. > This controller is currently not supported in > linux/drivers/ide/pdc202xx.c > It is possible to define this controller with the same behavior as > PDC20267 in linux/drivers/ide/pdc202xx.c? > Because the ARM-Integrator is not compatible to i386 is it possible > to get problems with the PDC-BIOS? > > Best regards > Frank > > PS: The Mailaddress of Frank Tiernan ([EMAIL PROTECTED]) is not valid. > Would you be so kind to give me his valid e-mail address ... > > -- > Dipl.-Ing. Elektrotechnik convergence integrated media gmbh / HW > Frank NeuberRosenthalerstr.51 / 10178 Berlin > Email: [EMAIL PROTECTED] Phone: +49(0)30-72 62 06 50 > WWW:www.convergence.de Fax:+49(0)30-72 62 06 55 > Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux support for PDC20268
Frank, Frank Tiernan does not exist at Promise anymore, and that company is HOSTILE towards Linux Now. On Tue, 5 Jun 2001, Frank Neuber wrote: Hi Andre, I try to set up IDE-Support for ARM-Integrator with an PDC20268. This controller is currently not supported in linux/drivers/ide/pdc202xx.c It is possible to define this controller with the same behavior as PDC20267 in linux/drivers/ide/pdc202xx.c? Because the ARM-Integrator is not compatible to i386 is it possible to get problems with the PDC-BIOS? Best regards Frank PS: The Mailaddress of Frank Tiernan ([EMAIL PROTECTED]) is not valid. Would you be so kind to give me his valid e-mail address ... -- Dipl.-Ing. Elektrotechnik convergence integrated media gmbh / HW Frank NeuberRosenthalerstr.51 / 10178 Berlin Email: [EMAIL PROTECTED] Phone: +49(0)30-72 62 06 50 WWW:www.convergence.de Fax:+49(0)30-72 62 06 55 Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: patch for ide.2.4.5-ac8
Thanks Todd,
Everyone knows that I was not an english major ;-)
Cheers,
On Tue, 5 Jun 2001, Todd M. Roy wrote:
> Andre,
> Minor typo fix:
> --- ide-dma.c.~1~ Tue Jun 5 14:39:06 2001
> +++ ide-dma.c Tue Jun 5 15:04:54 2001
> @@ -708,15 +708,15 @@
> if ((!dma_base) && (!second_chance)) {
> unsigned long set_bmiba = 0;
> second_chance++;
> - switch(dev->vender) {
> - PCI_VENDOR_ID_AL:
> - set_bmiba = DEFAULT_BMALIBA; break;
> - PCI_VENDOR_ID_VIA:
> - set_bmiba = DEFAULT_BMCRBA; break;
> - PCI_VENDOR_ID_INTEL:
> - set_bmiba = DEFAULT_BMIBA; break;
> - default:
> - return dma_base;
> + switch (dev->vendor) {
> + case PCI_VENDOR_ID_AL:
> + set_bmiba = DEFAULT_BMALIBA; break;
> + case PCI_VENDOR_ID_VIA:
> + set_bmiba = DEFAULT_BMCRBA; break;
> + case PCI_VENDOR_ID_INTEL:
> + set_bmiba = DEFAULT_BMIBA; break;
> + default:
> + return dma_base;
> }
> pci_write_config_dword(dev, 0x20, set_bmiba|1);
> goto second_chance_to_dma;
>
> Cheers,
> Todd
> **
> This footnote confirms that this email message has been swept by
> MIMEsweeper for the presence of computer viruses.
> **
>
Andre Hedrick
ASL Kernel Development
Linux ATA Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035Web: www.aslab.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: patch for ide.2.4.5-ac8
Thanks Todd,
Everyone knows that I was not an english major ;-)
Cheers,
On Tue, 5 Jun 2001, Todd M. Roy wrote:
Andre,
Minor typo fix:
--- ide-dma.c.~1~ Tue Jun 5 14:39:06 2001
+++ ide-dma.c Tue Jun 5 15:04:54 2001
@@ -708,15 +708,15 @@
if ((!dma_base) (!second_chance)) {
unsigned long set_bmiba = 0;
second_chance++;
- switch(dev-vender) {
- PCI_VENDOR_ID_AL:
- set_bmiba = DEFAULT_BMALIBA; break;
- PCI_VENDOR_ID_VIA:
- set_bmiba = DEFAULT_BMCRBA; break;
- PCI_VENDOR_ID_INTEL:
- set_bmiba = DEFAULT_BMIBA; break;
- default:
- return dma_base;
+ switch (dev-vendor) {
+ case PCI_VENDOR_ID_AL:
+ set_bmiba = DEFAULT_BMALIBA; break;
+ case PCI_VENDOR_ID_VIA:
+ set_bmiba = DEFAULT_BMCRBA; break;
+ case PCI_VENDOR_ID_INTEL:
+ set_bmiba = DEFAULT_BMIBA; break;
+ default:
+ return dma_base;
}
pci_write_config_dword(dev, 0x20, set_bmiba|1);
goto second_chance_to_dma;
Cheers,
Todd
**
This footnote confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
**
Andre Hedrick
ASL Kernel Development
Linux ATA Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035Web: www.aslab.com
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Speed to please all......
beetle:/src/DiskPerf-1.0.5 # ./DiskPerf.rw /dev/hdb Device: Maxtor 5T020H2 Serial Number: T2J0HC0C LBA 0 DMA Read Test = 68.82 MB/Sec (3.63 Seconds) Outer Diameter Sequential DMA Read Test = 36.68 MB/Sec (6.81 Seconds) Inner Diameter Sequential DMA Read Test = 21.36 MB/Sec (11.70 Seconds) LBA 1 DMA Write Test = 65.57 MB/Sec (3.81 Seconds) Outer Diameter Sequential DMA Write Test = 36.89 MB/Sec (6.78 Seconds) Inner Diameter Sequential DMA Write Test = 21.42 MB/Sec (11.67 Seconds) The new driver for 2.5 can read and write at near the same speeds. Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Speed to please all......
beetle:/src/DiskPerf-1.0.5 # ./DiskPerf.rw /dev/hdb Device: Maxtor 5T020H2 Serial Number: T2J0HC0C LBA 0 DMA Read Test = 68.82 MB/Sec (3.63 Seconds) Outer Diameter Sequential DMA Read Test = 36.68 MB/Sec (6.81 Seconds) Inner Diameter Sequential DMA Read Test = 21.36 MB/Sec (11.70 Seconds) LBA 1 DMA Write Test = 65.57 MB/Sec (3.81 Seconds) Outer Diameter Sequential DMA Write Test = 36.89 MB/Sec (6.78 Seconds) Inner Diameter Sequential DMA Write Test = 21.42 MB/Sec (11.67 Seconds) The new driver for 2.5 can read and write at near the same speeds. Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] HPT370 misc (for real this time)
+ p += sprintf(p, "\nController: %d\n", i); + p += sprintf(p, "Chipset: HPT%s\n", chipset_nums[class_rev]); + p += sprintf(p, "Bus speed: %d MHz\n", dev->bus->bus_speed); ^^^ DNE -- Does Not Exist + p += sprintf(p, "--- Primary Channel " + "--- Secondary Channel " + "--\n"); + Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] HPT370 misc (for real this time)
+ p += sprintf(p, \nController: %d\n, i); + p += sprintf(p, Chipset: HPT%s\n, chipset_nums[class_rev]); + p += sprintf(p, Bus speed: %d MHz\n, dev-bus-bus_speed); ^^^ DNE -- Does Not Exist + p += sprintf(p, --- Primary Channel + --- Secondary Channel + --\n); + Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Problem with kernel 2.2.19 Ultra-DMA and SMP, once more
If this is a VIA SMP system there are APIC problems that you do not want to even think about addressing. MPS1.1 and passing "noapic" will fix most of there mess, but you have a semi-crippled system, but it runs. On Fri, 1 Jun 2001 [EMAIL PROTECTED] wrote: > Hi once more... > > I'm sorry for the layout of this mail. It is written in a web mail > system... > The attachements are in ASCII format even if the web-mail make it base-64 > > Now I have compiled a vanilla 2.2.19 kernel and have SMP working, without > Ultra-DMA. I used the functional kernel config from 2.2.19-ide and just > activated SMP. > > >From that I have 3 very simular kernel configurations: > 2.2.19 with Hidrick's IDE-patch, no SMP: working > 2.2.19 without IDE-patch, with SMP: working > 2.2.19 with IDE-patch and SMP: not booting > > With all the information I hope that someone can help me with the > IDE-and-SMP > problem. > > _\\|//_ > (-0-0-) > /---ooO-(_)-Ooo--\ > | Magnus SandbergEmail: [EMAIL PROTECTED] | > | Network Engineer, Bluelabs http://www.bluelabs.se/ | > | Phone: +46-8-470 2155(FAX: +46-8-470 2199)GSM: +46-708-225 805 | > \/ > || || > ooO Ooo Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Problem with kernel 2.2.19 Ultra-DMA and SMP, once more
If this is a VIA SMP system there are APIC problems that you do not want to even think about addressing. MPS1.1 and passing noapic will fix most of there mess, but you have a semi-crippled system, but it runs. On Fri, 1 Jun 2001 [EMAIL PROTECTED] wrote: Hi once more... I'm sorry for the layout of this mail. It is written in a web mail system... The attachements are in ASCII format even if the web-mail make it base-64 Now I have compiled a vanilla 2.2.19 kernel and have SMP working, without Ultra-DMA. I used the functional kernel config from 2.2.19-ide and just activated SMP. From that I have 3 very simular kernel configurations: 2.2.19 with Hidrick's IDE-patch, no SMP: working 2.2.19 without IDE-patch, with SMP: working 2.2.19 with IDE-patch and SMP: not booting With all the information I hope that someone can help me with the IDE-and-SMP problem. _\\|//_ (-0-0-) /---ooO-(_)-Ooo--\ | Magnus SandbergEmail: [EMAIL PROTECTED] | | Network Engineer, Bluelabs http://www.bluelabs.se/ | | Phone: +46-8-470 2155(FAX: +46-8-470 2199)GSM: +46-708-225 805 | \/ || || ooO Ooo Andre Hedrick ASL Kernel Development Linux ATA Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Promise Ultra100 TX2 (105a:4d68)
Hi Eberhard, I have fixed that some time ago but patches are not being accepted. On Thu, 31 May 2001, Eberhard Moenkeberg wrote: > Date: Thu, 31 May 2001 09:35:27 +0200 (MET DST) > From: Eberhard Moenkeberg <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Promise Ultra100 TX2 (105a:4d68) > > Hi Andre, > > i have some new IDE PCI cards "Promise Ultra100 TX2", > and it seems that no linux kernel is able to detect > or use those chips (PCI ID 105a:4d68). > The chips are stamped PROMISE PDC 20268. > > Cheers -e > -- > Eberhard Moenkeberg ([EMAIL PROTECTED], [EMAIL PROTECTED]) > Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Promise Ultra100 TX2 (105a:4d68)
Hi Eberhard, I have fixed that some time ago but patches are not being accepted. On Thu, 31 May 2001, Eberhard Moenkeberg wrote: Date: Thu, 31 May 2001 09:35:27 +0200 (MET DST) From: Eberhard Moenkeberg [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Promise Ultra100 TX2 (105a:4d68) Hi Andre, i have some new IDE PCI cards Promise Ultra100 TX2, and it seems that no linux kernel is able to detect or use those chips (PCI ID 105a:4d68). The chips are stamped PROMISE PDC 20268. Cheers -e -- Eberhard Moenkeberg ([EMAIL PROTECTED], [EMAIL PROTECTED]) Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Promise Ultra100 TX2 pbm
Until I get some feed back that my patches will be accepted, there are a lot of fixes and updates on hold. Promise Ultra100 TX2, AMD760(MP), OSB4/CSB5. Right now there is a 2.2.19 patch and that is it. Since there are changes being made without understand the total scope of the issues at hand, one should expect more problems not less in the future. When I finish adding 48-lba addressing, I will post a patch for 2.4.5 but they will no longer be split up. There are to many reports of problems an the next patches will only be complete solutions to correct the current kludge mess that we have. Cheers, On Tue, 29 May 2001, Frederic Soulier wrote: > Hi Andre, > > Sorry to bother you, I know your time is precious, so pls feel free to > send this > to /dev/null if you don't have time :) > > I was wondering if the patch you issued on the 9th of April would fix > this problem. > I cannot set -d1 flag on the 2 disks on the Promise Ultra100 TX2 > > The throughput of my 2 hard disks on my Promise Controler is > ridiculous... > > # hdparm -t /dev/hda > > /dev/hda: > Timing buffered disk reads: 64 MB in 2.87 seconds = 22.30 MB/sec > > > # hdparm -t /dev/hde > > /dev/hde: > Timing buffered disk reads: 64 MB in 38.04 seconds = 1.68 MB/sec > > > # hdparm -t /dev/hdg > > /dev/hdg: > Timing buffered disk reads: 64 MB in 37.13 seconds = 1.72 MB/sec > > > .. maybe the reason is that I cannot set DMA for hde and hdf. I do not > understand. > > # hdparm -d1 /dev/hde >/dev/hde: > setting using_dma to 1 (on) > HDIO_SET_DMA failed: Operation not permitted > using_dma= 0 (off) > > # hdparm -d1 /dev/hdg >/dev/hdg: > setting using_dma to 1 (on) > HDIO_SET_DMA failed: Operation not permitted > using_dma= 0 (off) > > > Any help appreciated. > Thanks > Fred > > > 3 hard disks:- >(A) 1 IBM 37Gb ATA/66 on ide0 onboard controler >(B) 1 IBM 41Gb GXP60 ATA/100 on ide2 promise controler Ultra100 TX2 >(C) 1 IBM 25Gb ATA/66 on ide3 promise controler Ultra100 TX2 > > hdparm settings are: > > /dev/hda (A) > >/dev/hda: > multcount= 16 (on) > I/O support = 3 (32-bit w/sync) > unmaskirq= 1 (on) > using_dma= 1 (on) > keepsettings = 0 (off) > nowerr = 0 (off) > readonly = 0 (off) > readahead= 8 (on) >geometry = 4160/255/63, sectors = 66835440, start = 0 > > > /dev/hde (B) > >/dev/hde: > multcount= 16 (on) > I/O support = 3 (32-bit w/sync) > unmaskirq= 1 (on) > using_dma= 0 (off) > keepsettings = 0 (off) > nowerr = 0 (off) > readonly = 0 (off) > readahead= 8 (on) > geometry = 79780/16/63, sectors = 80418240, start = 0 > > > /dev/hdg (C) > >/dev/hdg: > multcount= 16 (on) > I/O support = 3 (32-bit w/sync) > unmaskirq= 1 (on) > using_dma= 0 (off) > keepsettings = 0 (off) > nowerr = 0 (off) > readonly = 0 (off) > readahead= 8 (on) > geometry = 53040/16/63, sectors = 53464320, start = 0 > Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Promise Ultra100 TX2 pbm
Until I get some feed back that my patches will be accepted, there are a lot of fixes and updates on hold. Promise Ultra100 TX2, AMD760(MP), OSB4/CSB5. Right now there is a 2.2.19 patch and that is it. Since there are changes being made without understand the total scope of the issues at hand, one should expect more problems not less in the future. When I finish adding 48-lba addressing, I will post a patch for 2.4.5 but they will no longer be split up. There are to many reports of problems an the next patches will only be complete solutions to correct the current kludge mess that we have. Cheers, On Tue, 29 May 2001, Frederic Soulier wrote: Hi Andre, Sorry to bother you, I know your time is precious, so pls feel free to send this to /dev/null if you don't have time :) I was wondering if the patch you issued on the 9th of April would fix this problem. I cannot set -d1 flag on the 2 disks on the Promise Ultra100 TX2 The throughput of my 2 hard disks on my Promise Controler is ridiculous... # hdparm -t /dev/hda /dev/hda: Timing buffered disk reads: 64 MB in 2.87 seconds = 22.30 MB/sec # hdparm -t /dev/hde /dev/hde: Timing buffered disk reads: 64 MB in 38.04 seconds = 1.68 MB/sec # hdparm -t /dev/hdg /dev/hdg: Timing buffered disk reads: 64 MB in 37.13 seconds = 1.72 MB/sec .. maybe the reason is that I cannot set DMA for hde and hdf. I do not understand. # hdparm -d1 /dev/hde /dev/hde: setting using_dma to 1 (on) HDIO_SET_DMA failed: Operation not permitted using_dma= 0 (off) # hdparm -d1 /dev/hdg /dev/hdg: setting using_dma to 1 (on) HDIO_SET_DMA failed: Operation not permitted using_dma= 0 (off) Any help appreciated. Thanks Fred 3 hard disks:- (A) 1 IBM 37Gb ATA/66 on ide0 onboard controler (B) 1 IBM 41Gb GXP60 ATA/100 on ide2 promise controler Ultra100 TX2 (C) 1 IBM 25Gb ATA/66 on ide3 promise controler Ultra100 TX2 hdparm settings are: /dev/hda (A) /dev/hda: multcount= 16 (on) I/O support = 3 (32-bit w/sync) unmaskirq= 1 (on) using_dma= 1 (on) keepsettings = 0 (off) nowerr = 0 (off) readonly = 0 (off) readahead= 8 (on) geometry = 4160/255/63, sectors = 66835440, start = 0 /dev/hde (B) /dev/hde: multcount= 16 (on) I/O support = 3 (32-bit w/sync) unmaskirq= 1 (on) using_dma= 0 (off) keepsettings = 0 (off) nowerr = 0 (off) readonly = 0 (off) readahead= 8 (on) geometry = 79780/16/63, sectors = 80418240, start = 0 /dev/hdg (C) /dev/hdg: multcount= 16 (on) I/O support = 3 (32-bit w/sync) unmaskirq= 1 (on) using_dma= 0 (off) keepsettings = 0 (off) nowerr = 0 (off) readonly = 0 (off) readahead= 8 (on) geometry = 53040/16/63, sectors = 53464320, start = 0 Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: pdc20268 error?
Not an error. The new PDC20268 has all the register data hidden form the user. Another anti-user-friendly reaction by Promise Technology. However, the up side is that they were smart enough to make the taskfile registers for the setfeatures command auto set the host values. Basically there are no data points that can be read from the new TX2 that have any real trustable world meaning. Cheers, On Tue, 29 May 2001, Vasile Gaburici wrote: > Date: Tue, 29 May 2001 22:41:38 -0400 (EDT) > From: Vasile Gaburici <[EMAIL PROTECTED]> > To: Andre Hedrick <[EMAIL PROTECTED]> > Subject: pdc20268 error? > > > Hi, > > I've got a Promise Ultra100 TX2 board to work with 2.2.19 plus > your ide.2.2.19.05042001 patch. I've only attached one UDMA33 capable > CD-ROM drive to the primary a channel of the card to see how things go. I > can mount access it okay (via hde). > > The fact that troubles me is that 'cat /proc/ide/pdc202xx' seems > to indicate that the board is in error and cannot determine PIO and DMA > modes for the devices (see attachments). Is this normal for my config or > is it a bug? > > Also, I'd like to know if the shortcuts in the driver for 20268 > (various gotos that skip code) are mandated by some improved hardware or > just lack of info for the 20268... > > > Thanks, > Vasile > > P.S.: Is there a list for ide-only discussion? 200/day on lklm is > too much for me... > Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Part I of Lameness...
Since this was filtered the first time...
Andre Hedrick
Linux ATA Development
-- Forwarded message --
Date: Mon, 28 May 2001 23:21:57 -0700 (PDT)
From: Andre Hedrick <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Lacking Performance my ARSE!
beetle:~ # hdparm -it /dev/hda
/dev/hda:
Model=Maxtor 5T020H2, FwRev=TAH71DP0, SerialNo=T2J0HBRC
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39062500
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4 udma5
Drive Supports : Reserved : ATA-1 ATA-2 ATA-3 ATA-4 ATA-5 ATA-6
Kernel Drive Geometry LogicalCHS=2431/255/63 PhysicalCHS=38752/16/63
Timing buffered disk reads: 64 MB in 1.75 seconds = 36.57 MB/sec
fttk:~ # hdparm -it /dev/hda
/dev/hda:
Model=IBM-DTLA-307020, FwRev=TX3OA50C, SerialNo=YHDYHT9S024
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40
BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=40188960
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Drive Supports : Reserved : ATA-2 ATA-3 ATA-4 ATA-5
Kernel Drive Geometry LogicalCHS=2501/255/63 PhysicalCHS=39870/16/63
Timing buffered disk reads: 64 MB in 1.81 seconds = 35.36 MB/sec
athy:~ # hdparm -it /dev/hda
/dev/hda:
Model=IBM-DTLA-307075, FwRev=TXAOA50C, SerialNo=YSDYSFA5874
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40
BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=150136560
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4 udma5
Drive Supports : Reserved : ATA-2 ATA-3 ATA-4 ATA-5
Kernel Drive Geometry LogicalCHS=9345/255/63 PhysicalCHS=148945/16/63
Timing buffered disk reads: 64 MB in 1.78 seconds = 35.96 MB/sec
Just because you can not configure your kernel correctly of have junk for
hardware or any other lame reason like a distro that does not know what
dma is..your problem not mine.
General bitching pisses me off, especially when you are dead wrong.
Regards,
Andre Hedrick
Linux ATA Development
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Part II of Lameness...
athy:/src/DiskPerf-1.0.4 # ./DiskPerf /dev/hda Device: IBM-DTLA-307075 Serial Number: YSDYSFA5874 LBA 0 DMA Read Test = 45.73 MB/Sec (5.47 Seconds) Outer Diameter Sequential DMA Read Test = 35.85 MB/Sec (6.97 Seconds) Inner Diameter Sequential DMA Read Test = 17.62 MB/Sec (14.19 Seconds) Sorry I do not have the other boxes configured with a kernel to accept this test callout. However I do have systems that rip at 63 MB/Sec and if you adjust for CR3's between kernel to user-space it comes out to about 93 MB/Sec. There is nothing LAME or LACKING about that performance! Regards, Andre Hedrick Linux ATA Development - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Part II of Lameness...
athy:/src/DiskPerf-1.0.4 # ./DiskPerf /dev/hda Device: IBM-DTLA-307075 Serial Number: YSDYSFA5874 LBA 0 DMA Read Test = 45.73 MB/Sec (5.47 Seconds) Outer Diameter Sequential DMA Read Test = 35.85 MB/Sec (6.97 Seconds) Inner Diameter Sequential DMA Read Test = 17.62 MB/Sec (14.19 Seconds) Sorry I do not have the other boxes configured with a kernel to accept this test callout. However I do have systems that rip at 63 MB/Sec and if you adjust for CR3's between kernel to user-space it comes out to about 93 MB/Sec. There is nothing LAME or LACKING about that performance! Regards, Andre Hedrick Linux ATA Development - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Part I of Lameness...
Since this was filtered the first time...
Andre Hedrick
Linux ATA Development
-- Forwarded message --
Date: Mon, 28 May 2001 23:21:57 -0700 (PDT)
From: Andre Hedrick [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Lacking Performance my ARSE!
beetle:~ # hdparm -it /dev/hda
/dev/hda:
Model=Maxtor 5T020H2, FwRev=TAH71DP0, SerialNo=T2J0HBRC
Config={ Fixed }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57
BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39062500
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4 udma5
Drive Supports : Reserved : ATA-1 ATA-2 ATA-3 ATA-4 ATA-5 ATA-6
Kernel Drive Geometry LogicalCHS=2431/255/63 PhysicalCHS=38752/16/63
Timing buffered disk reads: 64 MB in 1.75 seconds = 36.57 MB/sec
fttk:~ # hdparm -it /dev/hda
/dev/hda:
Model=IBM-DTLA-307020, FwRev=TX3OA50C, SerialNo=YHDYHT9S024
Config={ HardSect NotMFM HdSw15uSec Fixed DTR10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40
BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=40188960
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Drive Supports : Reserved : ATA-2 ATA-3 ATA-4 ATA-5
Kernel Drive Geometry LogicalCHS=2501/255/63 PhysicalCHS=39870/16/63
Timing buffered disk reads: 64 MB in 1.81 seconds = 35.36 MB/sec
athy:~ # hdparm -it /dev/hda
/dev/hda:
Model=IBM-DTLA-307075, FwRev=TXAOA50C, SerialNo=YSDYSFA5874
Config={ HardSect NotMFM HdSw15uSec Fixed DTR10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40
BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16, MultSect=16
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=150136560
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4 udma5
Drive Supports : Reserved : ATA-2 ATA-3 ATA-4 ATA-5
Kernel Drive Geometry LogicalCHS=9345/255/63 PhysicalCHS=148945/16/63
Timing buffered disk reads: 64 MB in 1.78 seconds = 35.96 MB/sec
Just because you can not configure your kernel correctly of have junk for
hardware or any other lame reason like a distro that does not know what
dma is..your problem not mine.
General bitching pisses me off, especially when you are dead wrong.
Regards,
Andre Hedrick
Linux ATA Development
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: pdc20268 error?
Not an error. The new PDC20268 has all the register data hidden form the user. Another anti-user-friendly reaction by Promise Technology. However, the up side is that they were smart enough to make the taskfile registers for the setfeatures command auto set the host values. Basically there are no data points that can be read from the new TX2 that have any real trustable world meaning. Cheers, On Tue, 29 May 2001, Vasile Gaburici wrote: Date: Tue, 29 May 2001 22:41:38 -0400 (EDT) From: Vasile Gaburici [EMAIL PROTECTED] To: Andre Hedrick [EMAIL PROTECTED] Subject: pdc20268 error? Hi, I've got a Promise Ultra100 TX2 board to work with 2.2.19 plus your ide.2.2.19.05042001 patch. I've only attached one UDMA33 capable CD-ROM drive to the primary a channel of the card to see how things go. I can mount access it okay (via hde). The fact that troubles me is that 'cat /proc/ide/pdc202xx' seems to indicate that the board is in error and cannot determine PIO and DMA modes for the devices (see attachments). Is this normal for my config or is it a bug? Also, I'd like to know if the shortcuts in the driver for 20268 (various gotos that skip code) are mandated by some improved hardware or just lack of info for the 20268... Thanks, Vasile P.S.: Is there a list for ide-only discussion? 200/day on lklm is too much for me... Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch]: ide dma timeout retry in pio
On Tue, 29 May 2001, Jens Axboe wrote: > This is bull shit. If IDE didn't muck around with the request so much in > the first place, the info could always be trusted. Even so, we have the > hard_* numbers to go by. So this argument does not hold. Maybe if you looked at the new code model as a whole you would see that the request-forking is gone. The object is to preserve a copy of the io instructions out to the registers to not have to repeat the do_request call unless it is a do or die thing. Also it is good to carry a copy of the local request even if it is never used. Also are you resetting the pointer (back to the geginning) on rq->buffer on the retry? You first flush the DMA engine and issue a device soft reset not using the current drive reset, is presevers the hwgroup->busy state and allows the request to be retried without reinserting. > > As I recall, there is a way to reinsert the faulted request, but that > > Again, look at the patch. The request is never off the list, so there is > never a reason to reinsert. hwgroup->busy is cleared (and, again for > good measure, hwgroup->rq), so ide_do_request/start_request will get the > same request that we just handled. I will have to poke in a few flags to verify this but if you say so. > > means the request_struct needs fault counter. If it is truly a DMA error > > ->errors, it's already there. Wrong location to poke and by that time it requires a full retry. The new code would have had the task structs filled with the error. > > because of re-seeks then the timeout value for that request must be > > expanded. > > Yep In some cases yes, but it would be better if I had a standard counter that meant something. Also changing the jiffie counter in ide_delay_50ms to a mdelay may have done more harm than good. Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch]: ide dma timeout retry in pio
On Tue, 29 May 2001, Jens Axboe wrote: This is bull shit. If IDE didn't muck around with the request so much in the first place, the info could always be trusted. Even so, we have the hard_* numbers to go by. So this argument does not hold. Maybe if you looked at the new code model as a whole you would see that the request-forking is gone. The object is to preserve a copy of the io instructions out to the registers to not have to repeat the do_request call unless it is a do or die thing. Also it is good to carry a copy of the local request even if it is never used. Also are you resetting the pointer (back to the geginning) on rq-buffer on the retry? You first flush the DMA engine and issue a device soft reset not using the current drive reset, is presevers the hwgroup-busy state and allows the request to be retried without reinserting. As I recall, there is a way to reinsert the faulted request, but that Again, look at the patch. The request is never off the list, so there is never a reason to reinsert. hwgroup-busy is cleared (and, again for good measure, hwgroup-rq), so ide_do_request/start_request will get the same request that we just handled. I will have to poke in a few flags to verify this but if you say so. means the request_struct needs fault counter. If it is truly a DMA error -errors, it's already there. Wrong location to poke and by that time it requires a full retry. The new code would have had the task structs filled with the error. because of re-seeks then the timeout value for that request must be expanded. Yep In some cases yes, but it would be better if I had a standard counter that meant something. Also changing the jiffie counter in ide_delay_50ms to a mdelay may have done more harm than good. Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] kmalloc checks for drivers/ide/ide-probe.c (244ac16)
On Fri, 25 May 2001, Rasmus Andersen wrote:
> On Fri, May 25, 2001 at 01:47:52PM -0700, Andre Hedrick wrote:
> >
> > Not valid because the jump to that part of the code is protected.
> > If a polling response for a valid status and no timeout, is detected then
> > it attempts to the command for real only after success or a test.
> >
> > Otherwise it would be valid.
/*
* try_to_identify() sends an ATA(PI) IDENTIFY request to a drive
* and waits for a response. It also monitors irqs while this is
* happening, in hope of automatically determining which one is
* being used by the interface.
*
* Returns: 0 device was identified
* 1 device timed-out (no response to identify request)
* 2 device aborted the command (refused to identify itself)
*/
static int actual_try_to_identify (ide_drive_t *drive, byte cmd)
{
if (OK_STAT(GET_STAT(),DRQ_STAT,BAD_R_STAT)) {
unsigned long flags;
__save_flags(flags);/* local CPU only */
__cli();/* local CPU only; some systems need this */
do_identify(drive, cmd); /* drive returned ID */
rc = 0; /* drive responded with ID */
(void) GET_STAT(); /* clear drive IRQ */
__restore_flags(flags); /* local CPU only */
} else
rc = 2; /* drive refused ID */
return rc;
}
If you get_stat returns a bad status we do not go into the test loop.
> So the EXABYTE case should return normally, I take (otherwise you
> confused me good;))? The patch below drops this change and keeps
> the rest.
/*
* probe_for_drive() tests for existence of a given drive using do_probe().
*
* Returns: 0 no device was found
* 1 device was found (note: drive->present might still be 0)
*/
static inline byte probe_for_drive (ide_drive_t *drive)
This calls out for the poke in the ribbon, and if it fail anywhere we
never get to the top function for the kmallocs.
Does that help?
This is potentially valid for modules but if it built in and you are out
of memory before partition checkinggo buy some memory. Also if you
are adding devices with a system under hard load eating/using memory to
that scale, you will have other issues to go KABOOM.
Will look at it for verification and run a gedanken process and get back
about it.
>
> --- linux-244-ac16-clean/drivers/ide/ide-probe.c Fri May 25 21:11:08 2001
> +++ linux-244-ac16/drivers/ide/ide-probe.cFri May 25 22:54:15 2001
> @@ -58,6 +58,11 @@
> struct hd_driveid *id;
>
> id = drive->id = kmalloc (SECTOR_WORDS*4, GFP_ATOMIC); /* called with
>interrupts disabled! */
> +if (!id) {
> +printk(KERN_WARNING "(ide-probe::do_identify) Out of memory.\n");
> +goto err_kmalloc;
> +}
> +
> ide_input_data(drive, id, SECTOR_WORDS);/* read 512 bytes of
>id info */
> ide__sti(); /* local CPU only */
> ide_fix_driveid(id);
> @@ -76,8 +81,7 @@
> if ((id->model[0] == 'P' && id->model[1] == 'M')
>|| (id->model[0] == 'S' && id->model[1] == 'K')) {
> printk("%s: EATA SCSI HBA %.10s\n", drive->name, id->model);
> - drive->present = 0;
> - return;
> +goto err_misc;
> }
> #endif /* CONFIG_SCSI_EATA_DMA || CONFIG_SCSI_EATA_PIO */
>
> @@ -111,8 +115,7 @@
> #ifdef CONFIG_BLK_DEV_PDC4030
> if (HWIF(drive)->channel == 1 && HWIF(drive)->chipset == ide_pdc4030) {
> printk(" -- not supported on 2nd Promise port\n");
> - drive->present = 0;
> - return;
> +goto err_misc;
> }
> #endif /* CONFIG_BLK_DEV_PDC4030 */
> switch (type) {
> @@ -174,6 +177,12 @@
> printk("ATA DISK drive\n");
> QUIRK_LIST(HWIF(drive),drive);
> return;
> +
> +err_misc:
> +kfree(id);
> +err_kmalloc:
> +drive->present = 0;
> +return;
> }
>
> /*
> @@ -759,11 +768,23 @@
> }
> minors= units * (1< gd= kmalloc (sizeof(struct gendisk), GFP_KERNEL);
> - gd->sizes = kmalloc (minors * sizeof(int), GFP_KERNEL);
> - gd->part = kmalloc (minors * sizeof(struct hd_struct), GFP_KERNEL);
> - bs= kmalloc (minors*sizeof(int), GFP_KERNEL);
> - max_sect = kmalloc (minors*sizeof(int), GFP_KERNEL);
> - max_ra= kmalloc (minors*sizeof(int), GFP_KERNEL);
> +if (!gd)
> +goto err_kmalloc_gd;
> +
Re: [PATCH] kmalloc checks for drivers/ide/ide-probe.c (244ac16)
Not valid because the jump to that part of the code is protected.
If a polling response for a valid status and no timeout, is detected then
it attempts to the command for real only after success or a test.
Otherwise it would be valid.
Cheers,
On Fri, 25 May 2001, Rasmus Andersen wrote:
> Date: Fri, 25 May 2001 22:18:13 +0200
> From: Rasmus Andersen <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: [PATCH] kmalloc checks for drivers/ide/ide-probe.c (244ac16)
>
> Hi.
>
> The following patch adds a number of checks for kmalloc returns
> to drivers/ide/ide-probe.c. It applies against ac16.
>
> One comment: This patch adds 'drive-present = 0' to the
> code path for the EXABYTE case. I could not discern if this was a
> shortcoming of the original code or not. Please comment.
>
>
> --- linux-244-ac16-clean/drivers/ide/ide-probe.c Fri May 25 21:11:08 2001
> +++ linux-244-ac16/drivers/ide/ide-probe.cFri May 25 21:51:08 2001
> @@ -58,6 +58,11 @@
> struct hd_driveid *id;
>
> id = drive->id = kmalloc (SECTOR_WORDS*4, GFP_ATOMIC); /* called with
>interrupts disabled! */
> +if (!id) {
> +printk(KERN_WARNING "(ide-probe::do_identify) Out of memory.\n");
> +goto err_kmalloc;
> +}
> +
> ide_input_data(drive, id, SECTOR_WORDS);/* read 512 bytes of
>id info */
> ide__sti(); /* local CPU only */
> ide_fix_driveid(id);
> @@ -76,8 +81,7 @@
> if ((id->model[0] == 'P' && id->model[1] == 'M')
>|| (id->model[0] == 'S' && id->model[1] == 'K')) {
> printk("%s: EATA SCSI HBA %.10s\n", drive->name, id->model);
> - drive->present = 0;
> - return;
> +goto err_misc;
> }
> #endif /* CONFIG_SCSI_EATA_DMA || CONFIG_SCSI_EATA_PIO */
>
> @@ -96,7 +100,7 @@
> ide_fixstring (id->serial_no, sizeof(id->serial_no), bswap);
>
> if (strstr(id->model, "E X A B Y T E N E S T"))
> - return;
> +goto err_misc;
>
> id->model[sizeof(id->model)-1] = '\0'; /* we depend on this a lot! */
> printk("%s: %s, ", drive->name, id->model);
> @@ -111,8 +115,7 @@
> #ifdef CONFIG_BLK_DEV_PDC4030
> if (HWIF(drive)->channel == 1 && HWIF(drive)->chipset == ide_pdc4030) {
> printk(" -- not supported on 2nd Promise port\n");
> - drive->present = 0;
> - return;
> +goto err_misc;
> }
> #endif /* CONFIG_BLK_DEV_PDC4030 */
> switch (type) {
> @@ -174,6 +177,12 @@
> printk("ATA DISK drive\n");
> QUIRK_LIST(HWIF(drive),drive);
> return;
> +
> +err_misc:
> +kfree(id);
> +err_kmalloc:
> +drive->present = 0;
> +return;
> }
>
> /*
> @@ -759,11 +768,23 @@
> }
> minors= units * (1< gd= kmalloc (sizeof(struct gendisk), GFP_KERNEL);
> - gd->sizes = kmalloc (minors * sizeof(int), GFP_KERNEL);
> - gd->part = kmalloc (minors * sizeof(struct hd_struct), GFP_KERNEL);
> - bs= kmalloc (minors*sizeof(int), GFP_KERNEL);
> - max_sect = kmalloc (minors*sizeof(int), GFP_KERNEL);
> - max_ra= kmalloc (minors*sizeof(int), GFP_KERNEL);
> +if (!gd)
> +goto err_kmalloc_gd;
> +gd->sizes = kmalloc (minors * sizeof(int), GFP_KERNEL);
> +if (!gd->sizes)
> +goto err_kmalloc_gd_sizes;
> +gd->part = kmalloc (minors * sizeof(struct hd_struct), GFP_KERNEL);
> +if (!gd->part)
> +goto err_kmalloc_gd_part;
> +bs= kmalloc (minors*sizeof(int), GFP_KERNEL);
> +if (!bs)
> +goto err_kmalloc_gs;
> +max_sect = kmalloc (minors*sizeof(int), GFP_KERNEL);
> +if (!max_sect)
> +goto err_kmalloc_max_sect;
> +max_ra= kmalloc (minors*sizeof(int), GFP_KERNEL);
> +if (!max_ra)
> +goto err_kmalloc_max_ra;
>
> memset(gd->part, 0, minors * sizeof(struct hd_struct));
>
> @@ -816,6 +837,21 @@
> devfs_mk_dir (ide_devfs_handle, name, NULL);
> }
> }
> +return;
> +
> +err_kmalloc_max_ra:
> +kfree(max_sect);
> +err_kmalloc_max_sect:
> +kfree(bs);
> +err_kmalloc_gs:
> +kfree(gd->part);
> +err_kmalloc_gd_part:
> +kfree(gd-&g
Re: [PATCH] kmalloc checks for drivers/ide/ide-probe.c (244ac16)
Not valid because the jump to that part of the code is protected.
If a polling response for a valid status and no timeout, is detected then
it attempts to the command for real only after success or a test.
Otherwise it would be valid.
Cheers,
On Fri, 25 May 2001, Rasmus Andersen wrote:
Date: Fri, 25 May 2001 22:18:13 +0200
From: Rasmus Andersen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: [PATCH] kmalloc checks for drivers/ide/ide-probe.c (244ac16)
Hi.
The following patch adds a number of checks for kmalloc returns
to drivers/ide/ide-probe.c. It applies against ac16.
One comment: This patch adds 'drive-present = 0' to the
code path for the EXABYTE case. I could not discern if this was a
shortcoming of the original code or not. Please comment.
--- linux-244-ac16-clean/drivers/ide/ide-probe.c Fri May 25 21:11:08 2001
+++ linux-244-ac16/drivers/ide/ide-probe.cFri May 25 21:51:08 2001
@@ -58,6 +58,11 @@
struct hd_driveid *id;
id = drive-id = kmalloc (SECTOR_WORDS*4, GFP_ATOMIC); /* called with
interrupts disabled! */
+if (!id) {
+printk(KERN_WARNING (ide-probe::do_identify) Out of memory.\n);
+goto err_kmalloc;
+}
+
ide_input_data(drive, id, SECTOR_WORDS);/* read 512 bytes of
id info */
ide__sti(); /* local CPU only */
ide_fix_driveid(id);
@@ -76,8 +81,7 @@
if ((id-model[0] == 'P' id-model[1] == 'M')
|| (id-model[0] == 'S' id-model[1] == 'K')) {
printk(%s: EATA SCSI HBA %.10s\n, drive-name, id-model);
- drive-present = 0;
- return;
+goto err_misc;
}
#endif /* CONFIG_SCSI_EATA_DMA || CONFIG_SCSI_EATA_PIO */
@@ -96,7 +100,7 @@
ide_fixstring (id-serial_no, sizeof(id-serial_no), bswap);
if (strstr(id-model, E X A B Y T E N E S T))
- return;
+goto err_misc;
id-model[sizeof(id-model)-1] = '\0'; /* we depend on this a lot! */
printk(%s: %s, , drive-name, id-model);
@@ -111,8 +115,7 @@
#ifdef CONFIG_BLK_DEV_PDC4030
if (HWIF(drive)-channel == 1 HWIF(drive)-chipset == ide_pdc4030) {
printk( -- not supported on 2nd Promise port\n);
- drive-present = 0;
- return;
+goto err_misc;
}
#endif /* CONFIG_BLK_DEV_PDC4030 */
switch (type) {
@@ -174,6 +177,12 @@
printk(ATA DISK drive\n);
QUIRK_LIST(HWIF(drive),drive);
return;
+
+err_misc:
+kfree(id);
+err_kmalloc:
+drive-present = 0;
+return;
}
/*
@@ -759,11 +768,23 @@
}
minors= units * (1PARTN_BITS);
gd= kmalloc (sizeof(struct gendisk), GFP_KERNEL);
- gd-sizes = kmalloc (minors * sizeof(int), GFP_KERNEL);
- gd-part = kmalloc (minors * sizeof(struct hd_struct), GFP_KERNEL);
- bs= kmalloc (minors*sizeof(int), GFP_KERNEL);
- max_sect = kmalloc (minors*sizeof(int), GFP_KERNEL);
- max_ra= kmalloc (minors*sizeof(int), GFP_KERNEL);
+if (!gd)
+goto err_kmalloc_gd;
+gd-sizes = kmalloc (minors * sizeof(int), GFP_KERNEL);
+if (!gd-sizes)
+goto err_kmalloc_gd_sizes;
+gd-part = kmalloc (minors * sizeof(struct hd_struct), GFP_KERNEL);
+if (!gd-part)
+goto err_kmalloc_gd_part;
+bs= kmalloc (minors*sizeof(int), GFP_KERNEL);
+if (!bs)
+goto err_kmalloc_gs;
+max_sect = kmalloc (minors*sizeof(int), GFP_KERNEL);
+if (!max_sect)
+goto err_kmalloc_max_sect;
+max_ra= kmalloc (minors*sizeof(int), GFP_KERNEL);
+if (!max_ra)
+goto err_kmalloc_max_ra;
memset(gd-part, 0, minors * sizeof(struct hd_struct));
@@ -816,6 +837,21 @@
devfs_mk_dir (ide_devfs_handle, name, NULL);
}
}
+return;
+
+err_kmalloc_max_ra:
+kfree(max_sect);
+err_kmalloc_max_sect:
+kfree(bs);
+err_kmalloc_gs:
+kfree(gd-part);
+err_kmalloc_gd_part:
+kfree(gd-sizes);
+err_kmalloc_gd_sizes:
+kfree(gd);
+err_kmalloc_gd:
+printk(KERN_WARNING (ide::init_gendisk) Out of memory\n);
+return;
}
static int hwif_init (ide_hwif_t *hwif)
--
regards,
Rasmus([EMAIL PROTECTED])
An Emacs reference mug is what I want. It would hold ten gallons of
coffee. -- Steve VanDevender
Andre Hedrick
Linux ATA Development
ASL Kernel Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035
Re: [PATCH] kmalloc checks for drivers/ide/ide-probe.c (244ac16)
On Fri, 25 May 2001, Rasmus Andersen wrote:
On Fri, May 25, 2001 at 01:47:52PM -0700, Andre Hedrick wrote:
Not valid because the jump to that part of the code is protected.
If a polling response for a valid status and no timeout, is detected then
it attempts to the command for real only after success or a test.
Otherwise it would be valid.
/*
* try_to_identify() sends an ATA(PI) IDENTIFY request to a drive
* and waits for a response. It also monitors irqs while this is
* happening, in hope of automatically determining which one is
* being used by the interface.
*
* Returns: 0 device was identified
* 1 device timed-out (no response to identify request)
* 2 device aborted the command (refused to identify itself)
*/
static int actual_try_to_identify (ide_drive_t *drive, byte cmd)
{
snip
if (OK_STAT(GET_STAT(),DRQ_STAT,BAD_R_STAT)) {
unsigned long flags;
__save_flags(flags);/* local CPU only */
__cli();/* local CPU only; some systems need this */
do_identify(drive, cmd); /* drive returned ID */
rc = 0; /* drive responded with ID */
(void) GET_STAT(); /* clear drive IRQ */
__restore_flags(flags); /* local CPU only */
} else
rc = 2; /* drive refused ID */
return rc;
}
If you get_stat returns a bad status we do not go into the test loop.
So the EXABYTE case should return normally, I take (otherwise you
confused me good;))? The patch below drops this change and keeps
the rest.
/*
* probe_for_drive() tests for existence of a given drive using do_probe().
*
* Returns: 0 no device was found
* 1 device was found (note: drive-present might still be 0)
*/
static inline byte probe_for_drive (ide_drive_t *drive)
This calls out for the poke in the ribbon, and if it fail anywhere we
never get to the top function for the kmallocs.
Does that help?
This is potentially valid for modules but if it built in and you are out
of memory before partition checkinggo buy some memory. Also if you
are adding devices with a system under hard load eating/using memory to
that scale, you will have other issues to go KABOOM.
Will look at it for verification and run a gedanken process and get back
about it.
--- linux-244-ac16-clean/drivers/ide/ide-probe.c Fri May 25 21:11:08 2001
+++ linux-244-ac16/drivers/ide/ide-probe.cFri May 25 22:54:15 2001
@@ -58,6 +58,11 @@
struct hd_driveid *id;
id = drive-id = kmalloc (SECTOR_WORDS*4, GFP_ATOMIC); /* called with
interrupts disabled! */
+if (!id) {
+printk(KERN_WARNING (ide-probe::do_identify) Out of memory.\n);
+goto err_kmalloc;
+}
+
ide_input_data(drive, id, SECTOR_WORDS);/* read 512 bytes of
id info */
ide__sti(); /* local CPU only */
ide_fix_driveid(id);
@@ -76,8 +81,7 @@
if ((id-model[0] == 'P' id-model[1] == 'M')
|| (id-model[0] == 'S' id-model[1] == 'K')) {
printk(%s: EATA SCSI HBA %.10s\n, drive-name, id-model);
- drive-present = 0;
- return;
+goto err_misc;
}
#endif /* CONFIG_SCSI_EATA_DMA || CONFIG_SCSI_EATA_PIO */
@@ -111,8 +115,7 @@
#ifdef CONFIG_BLK_DEV_PDC4030
if (HWIF(drive)-channel == 1 HWIF(drive)-chipset == ide_pdc4030) {
printk( -- not supported on 2nd Promise port\n);
- drive-present = 0;
- return;
+goto err_misc;
}
#endif /* CONFIG_BLK_DEV_PDC4030 */
switch (type) {
@@ -174,6 +177,12 @@
printk(ATA DISK drive\n);
QUIRK_LIST(HWIF(drive),drive);
return;
+
+err_misc:
+kfree(id);
+err_kmalloc:
+drive-present = 0;
+return;
}
/*
@@ -759,11 +768,23 @@
}
minors= units * (1PARTN_BITS);
gd= kmalloc (sizeof(struct gendisk), GFP_KERNEL);
- gd-sizes = kmalloc (minors * sizeof(int), GFP_KERNEL);
- gd-part = kmalloc (minors * sizeof(struct hd_struct), GFP_KERNEL);
- bs= kmalloc (minors*sizeof(int), GFP_KERNEL);
- max_sect = kmalloc (minors*sizeof(int), GFP_KERNEL);
- max_ra= kmalloc (minors*sizeof(int), GFP_KERNEL);
+if (!gd)
+goto err_kmalloc_gd;
+gd-sizes = kmalloc (minors * sizeof(int), GFP_KERNEL);
+if (!gd-sizes)
+goto err_kmalloc_gd_sizes;
+gd-part = kmalloc (minors * sizeof(struct hd_struct), GFP_KERNEL);
+if (!gd-part)
+goto err_kmalloc_gd_part;
+bs= kmalloc (minors*sizeof(int), GFP_KERNEL);
+if (!bs)
+goto err_kmalloc_gs;
+max_sect = kmalloc (minors*sizeof
Re: Linux-Kernel Archive: ide-floppy
On Thu, 17 May 2001, Alan Cox wrote: > Date: Thu, 17 May 2001 23:58:52 +0100 (BST) > > > As for AC patches have not gotten around to messing with, but I have a few > > reported cases where stock or pre-patched linus-trees work and > > pre-patched ac-trees fail... > > If people can pin down cases where -ac fails and the main tree doesnt that > would be good. There shouldnt be any differences that matter but apparently there > are Thump "StoatWblr" about the ali crash... Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-Kernel Archive: ide-floppy
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0105.2/0082.html > Whenever I boot (2.4.4-ac6) I get this error message if there is a zip > disk in the drive. > > hdb: 98288kB, 196576 blocks, 512 sector size, hdb: 98304kB, 96/64/32 CHS, > 4096 kBps, 512 sector size, 2941 rpm ide-floppy: hdb: I/O error, pc = 5a, > key = 5, asc = 24, ascq = 0 > > The drive seems to work fine for everything except writing large files > (>500k) - umount hangs indefinitely. This has been a problem for all the > kernels I've used since I got the drive (2.2.18, 2.2.20, 2.4.0->2.4.4-ac6 > series). The ide-floppy support is compiled into the kernel but I've had > similar problems when using it as a module. The disks work perfectly on a > windows box and even worked fine when I was using the drive with windows. > > Can anyone shed any light on this for me? Linux p6dnf 2.4.5-pre2 #1 SMP Thu May 17 14:46:10 PDT 2001 i686 unknown Well I dusted of the device an chucked it into a box via handy-dandy hotswap shuttle and.. May 17 15:29:59 p6dnf kernel: hdl: 98304kB, 196608 blocks, 512 sector size, May 17 15:29:59 p6dnf kernel: hdl: 98304kB, 32/64/96 CHS, 4096 kBps, 512 sector size, 2941 rpm Pop the module out and back in and ... May 17 15:46:58 p6dnf kernel: hdl: 98304kB, 32/64/96 CHS, 4096 kBps, 512 sector size, 2941 rpm As for AC patches have not gotten around to messing with, but I have a few reported cases where stock or pre-patched linus-trees work and pre-patched ac-trees fail... So you got me on that one. -- Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-Kernel Archive: ATA overlap/queuing support ?
Is there support in linux for ATA overlap/queuing ? It should ( among other things ) improve concurent performance of two devices on the same channel. -- David Balazic -- > http://www.uwsg.indiana.edu/hypermail/linux/kernel/0105.2/0022.html No, queuing is broken and requires a special host to do the auto-polling. Right now only HighPoint has a host that will perform that operation. Also it requires TFAM and that will not be include until 2.5. ATA-overlap or ATAPI-overlap? The later is known as DSC based on SFF-8020/8070/8090, I have forgotten where it is located but I have the docs, and it is supported in ide-floppy and ide-tape. Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Updates...ide.2.4.5-p1.05132001...FastTrak...CSB5...AMD761
What did we do First we added two things for the Promise owners. If you have a FastTrak and you wish to use it in normal mode, we have a solution now. Place all the drives in "span" with only one drive per array. This makes each array a single device. This will work; however, you must set the new Promise Option to enable the HOST regardless. Do not set this option with Promise's I2O card! CSB5...erm it is a work in progress but should be fully functional in 24-48 hours. AMD761 is fully functional upto ATA-66, the ATA-100 feature is not complete, but will register so...if you board works great, otherwise issue an hdparm -X68 /dev/hdX to set the HOST into ATA-66 mode. The dreaded timeout is actively being killed. The mystery of hot-swap, well see LANANA threadsince there is a freeze on char-major-10-XXX device points, thus there is a freeeze on this code coming to Linux. :-( I hope to have all of this cleaned up and ready for submission for the pre3/4/5 patch releases. Cheers, Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Updates...ide.2.4.5-p1.05132001...FastTrak...CSB5...AMD761
What did we do First we added two things for the Promise owners. If you have a FastTrak and you wish to use it in normal mode, we have a solution now. Place all the drives in span with only one drive per array. This makes each array a single device. This will work; however, you must set the new Promise Option to enable the HOST regardless. Do not set this option with Promise's I2O card! CSB5...erm it is a work in progress but should be fully functional in 24-48 hours. AMD761 is fully functional upto ATA-66, the ATA-100 feature is not complete, but will register so...if you board works great, otherwise issue an hdparm -X68 /dev/hdX to set the HOST into ATA-66 mode. The dreaded timeout is actively being killed. The mystery of hot-swap, well see LANANA threadsince there is a freeze on char-major-10-XXX device points, thus there is a freeeze on this code coming to Linux. :-( I hope to have all of this cleaned up and ready for submission for the pre3/4/5 patch releases. Cheers, Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-Kernel Archive: ATA overlap/queuing support ?
Is there support in linux for ATA overlap/queuing ? It should ( among other things ) improve concurent performance of two devices on the same channel. -- David Balazic -- http://www.uwsg.indiana.edu/hypermail/linux/kernel/0105.2/0022.html No, queuing is broken and requires a special host to do the auto-polling. Right now only HighPoint has a host that will perform that operation. Also it requires TFAM and that will not be include until 2.5. ATA-overlap or ATAPI-overlap? The later is known as DSC based on SFF-8020/8070/8090, I have forgotten where it is located but I have the docs, and it is supported in ide-floppy and ide-tape. Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-Kernel Archive: ide-floppy
http://www.uwsg.indiana.edu/hypermail/linux/kernel/0105.2/0082.html Whenever I boot (2.4.4-ac6) I get this error message if there is a zip disk in the drive. hdb: 98288kB, 196576 blocks, 512 sector size, hdb: 98304kB, 96/64/32 CHS, 4096 kBps, 512 sector size, 2941 rpm ide-floppy: hdb: I/O error, pc = 5a, key = 5, asc = 24, ascq = 0 The drive seems to work fine for everything except writing large files (500k) - umount hangs indefinitely. This has been a problem for all the kernels I've used since I got the drive (2.2.18, 2.2.20, 2.4.0-2.4.4-ac6 series). The ide-floppy support is compiled into the kernel but I've had similar problems when using it as a module. The disks work perfectly on a windows box and even worked fine when I was using the drive with windows. Can anyone shed any light on this for me? Linux p6dnf 2.4.5-pre2 #1 SMP Thu May 17 14:46:10 PDT 2001 i686 unknown Well I dusted of the device an chucked it into a box via handy-dandy hotswap shuttle and.. May 17 15:29:59 p6dnf kernel: hdl: 98304kB, 196608 blocks, 512 sector size, May 17 15:29:59 p6dnf kernel: hdl: 98304kB, 32/64/96 CHS, 4096 kBps, 512 sector size, 2941 rpm Pop the module out and back in and ... May 17 15:46:58 p6dnf kernel: hdl: 98304kB, 32/64/96 CHS, 4096 kBps, 512 sector size, 2941 rpm As for AC patches have not gotten around to messing with, but I have a few reported cases where stock or pre-patched linus-trees work and pre-patched ac-trees fail... So you got me on that one. -- Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-Kernel Archive: ide-floppy
On Thu, 17 May 2001, Alan Cox wrote: Date: Thu, 17 May 2001 23:58:52 +0100 (BST) As for AC patches have not gotten around to messing with, but I have a few reported cases where stock or pre-patched linus-trees work and pre-patched ac-trees fail... If people can pin down cases where -ac fails and the main tree doesnt that would be good. There shouldnt be any differences that matter but apparently there are Thump StoatWblr about the ali crash... Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: HPT370 raid hack
COOL... We can take a look and see. On Mon, 7 May 2001, Wilfried Weissmann wrote: > Hi! > > I just put my highpoint-tech raid hack on a website: > http://www.rug-rats.org/~wilfried/ > So if you want to play around with it you can download it from there + > get a mininum of documentation. > > Andre Hedric, Ajran van de Ven, ...: > I am sorry that I did not had much time lately to get some information > of the > raid layout written together. But I did not forget you guys... > > regard, > Wilfried > Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: HPT370 raid hack
COOL... We can take a look and see. On Mon, 7 May 2001, Wilfried Weissmann wrote: Hi! I just put my highpoint-tech raid hack on a website: http://www.rug-rats.org/~wilfried/ So if you want to play around with it you can download it from there + get a mininum of documentation. Andre Hedric, Ajran van de Ven, ...: I am sorry that I did not had much time lately to get some information of the raid layout written together. But I did not forget you guys... regard, Wilfried Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Hotswap ATA status ?
On Mon, 7 May 2001, David Balazic wrote: > > Andre , you promised ATA/IDE hot-swap on "normal" hardware > several weeks ( months ? ) ago. What happened ? > > -- > David Balazic > -- > "Be excellent to each other." - Bill & Ted > - - - - - - - - - - - - - - - - - - - - - - > Well lets see. I lost my ISP (NorthPoint + PacBell)4/18/2001 There was a T13 meeting the following week. 4/23/2001 Found a flaw in the tests of writecaching. Reverified the contents of the CODE base to match SPEC 4/29/2001 Reverified that certain hosts are not good. (oh two kids that were ill and then the wife) Reconfigure the "CAVE" where I do all of my work. Write 90% of 48-bit LBA, use/test the hostswap for large/huge drives. Look at the user API and chuckled then cried and roared aloud.. Figure out License for the "ide-service.o" module. It will not be GPL but a very strict LAD (BSD-ish) License. Reasons will follow, but I will not be liable for stupid usage. So if you are reallying dying to test code that has not been full shaken down and requires a huge page for the glue, I will post one. The service utility is not ready yet so it is no good without one. Regards, Andre Hedrick Linux ATA Development PS I left a dump here and there.but that was going to be WTMI - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Hotswap ATA status ?
On Mon, 7 May 2001, David Balazic wrote: Andre , you promised ATA/IDE hot-swap on normal hardware several weeks ( months ? ) ago. What happened ? -- David Balazic -- Be excellent to each other. - Bill Ted - - - - - - - - - - - - - - - - - - - - - - Well lets see. I lost my ISP (NorthPoint + PacBell)4/18/2001 There was a T13 meeting the following week. 4/23/2001 Found a flaw in the tests of writecaching. Reverified the contents of the CODE base to match SPEC 4/29/2001 Reverified that certain hosts are not good. (oh two kids that were ill and then the wife) Reconfigure the CAVE where I do all of my work. Write 90% of 48-bit LBA, use/test the hostswap for large/huge drives. Look at the user API and chuckled then cried and roared aloud.. Figure out License for the ide-service.o module. It will not be GPL but a very strict LAD (BSD-ish) License. Reasons will follow, but I will not be liable for stupid usage. So if you are reallying dying to test code that has not been full shaken down and requires a huge page for the glue, I will post one. The service utility is not ready yet so it is no good without one. Regards, Andre Hedrick Linux ATA Development PS I left a dump here and there.but that was going to be WTMI - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Help with Fasttrack/100 Raid on Linux
On Tue, 17 Apr 2001, Wilfried Weissmann wrote: > Andre Hedrick wrote: > > > > Wilfried, > > > > Why a module? > > The idea behind that was that, if it is a seperate module, then it would be easier >to maintain for > me. I am a guy that always needs the newest and greatest, so I expected that I would >have to port my > stuff to newer kernels frequently. (I started the HPT-RAID0 alone without much >knowledge about the > kernel.) > > > Why not have the detection and flags that hook the md driver for linux and > > use linux's software raid? > > I could not use the disk striping, because of the raid0 code is not capable of >processing a request > what would span more than one disk. You also have to shift the offset of all but the >first disk by > 10 sectors. So I created an own personality... > > I also guess it would be a bit complicated if we want to create a raid10. Is this >done by putting a > raid1 over raid0 devices? We would have to find a way to map the sectors according >to the IDE-RAID > spec of the controller over several raid levels. > An ataraid personality would be easier and more flexible then. > > regards, > Wilfried Hello Wilfried, The really easy thing to do is to come up with the personality rules you want to se and let me create the API. I can make drives talk, listen, dance, spin, flip, etc. Raid 0 and Raid 1 are cakewalks, if you have the right tools. These will be around in 2.5. All you need to do is tell me what you want the subsystem to do. When you want it done and the observer's view of the operations. I can do things like threaded-parallel PRD building for DMA with the tap of a keystroke of two. I can commit the purfect lie in storage and destroke a drive to the view of the OS and then do switch-buffer PRD building. If you want it on 2,3,4,N drives I can do it with fast simple legal trick code. During INIT process I can protect the drive in ways you have never considered. I can access the whole drive even of the OS only knows only a portion of the real capacity. And I do not need silly and foolosh means like "bread". I tell it, "Hey dude, we are running under a lie. Go sneak off to the head or tail of the drive and get me that raid-voodoo-bios-os communication transport layer, and do it ins DMA modes, NOW!" I do not have the desire to do personality tables, but I can. We will not need any new majors because there is plenty of space in the ones we have, and 128 minors/channel is enough to do anything. If you want to do your module cool, but I promise you it will break in 2.5 and you will not know for months what hit you. I personally would like to avoid this issue of wreckin work. Second, if you think changes to the driver made by you have a chance in hell to make the kernel, I am not allowed to fixed the driver today to address the needs and correct current issues and ones coming down the pipe. With about 96% of all linux boxes in the world dependent on some form of ATA/ATAPI, Linus and Alan are very sensitive to even the sligthest change. Cheers, Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Help with Fasttrack/100 Raid on Linux
On Tue, 17 Apr 2001, Wilfried Weissmann wrote: Andre Hedrick wrote: Wilfried, Why a module? The idea behind that was that, if it is a seperate module, then it would be easier to maintain for me. I am a guy that always needs the newest and greatest, so I expected that I would have to port my stuff to newer kernels frequently. (I started the HPT-RAID0 alone without much knowledge about the kernel.) Why not have the detection and flags that hook the md driver for linux and use linux's software raid? I could not use the disk striping, because of the raid0 code is not capable of processing a request what would span more than one disk. You also have to shift the offset of all but the first disk by 10 sectors. So I created an own personality... I also guess it would be a bit complicated if we want to create a raid10. Is this done by putting a raid1 over raid0 devices? We would have to find a way to map the sectors according to the IDE-RAID spec of the controller over several raid levels. An ataraid personality would be easier and more flexible then. regards, Wilfried Hello Wilfried, The really easy thing to do is to come up with the personality rules you want to se and let me create the API. I can make drives talk, listen, dance, spin, flip, etc. Raid 0 and Raid 1 are cakewalks, if you have the right tools. These will be around in 2.5. All you need to do is tell me what you want the subsystem to do. When you want it done and the observer's view of the operations. I can do things like threaded-parallel PRD building for DMA with the tap of a keystroke of two. I can commit the purfect lie in storage and destroke a drive to the view of the OS and then do switch-buffer PRD building. If you want it on 2,3,4,N drives I can do it with fast simple legal trick code. During INIT process I can protect the drive in ways you have never considered. I can access the whole drive even of the OS only knows only a portion of the real capacity. And I do not need silly and foolosh means like "bread". I tell it, "Hey dude, we are running under a lie. Go sneak off to the head or tail of the drive and get me that raid-voodoo-bios-os communication transport layer, and do it ins DMA modes, NOW!" I do not have the desire to do personality tables, but I can. We will not need any new majors because there is plenty of space in the ones we have, and 128 minors/channel is enough to do anything. If you want to do your module cool, but I promise you it will break in 2.5 and you will not know for months what hit you. I personally would like to avoid this issue of wreckin work. Second, if you think changes to the driver made by you have a chance in hell to make the kernel, I am not allowed to fixed the driver today to address the needs and correct current issues and ones coming down the pipe. With about 96% of all linux boxes in the world dependent on some form of ATA/ATAPI, Linus and Alan are very sensitive to even the sligthest change. Cheers, Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Help with Fasttrack/100 Raid on Linux
Wilfried, Why a module? Why not have the detection and flags that hook the md driver for linux and use linux's software raid? Cheers, On Mon, 16 Apr 2001, Wilfried Weissmann wrote: > Arjan van de Ven wrote: > > > > In article <[EMAIL PROTECTED]> you wrote: > > > Andre Hedrick wrote: > > > > > However as far as I can see everyone who has a FastTrak which is "stuck" > > > in RAID mode[1] would be happy if it worked as a normal IDE controller > > > in Linux, which is (usually?) not the case - eg on the MSI board where > > > only the first channel is seen. > > > > I have a patch to work around that. However the better solution would be to > > have a native driver for the raid; I plan to start working on that next > > week... > > I am doing the same for the HighPoint-Tech 370 (talking about the RAID driver). >Disk-striping is > working so far. My code is based on the kernel patches for MDs from Neil Brown. I >created an own > RAID-personality for the module. > When I looked at the FreeBSD implementation I had the idea of making a "supermodule" >which could > contain serveral IDE-RAID drivers (e.g.: Proise FastTrack + HPT370). There would be >a super > personality for ATA-RAID and several low-level drivers for the individual >controllers. > > Interrested? Ideas? Hints, Tips, ...? Wanna team up? <8) > > > > > Greetings, > > Arjan van de Ven > > regards, > Wilfried > > PS: An uppercase THANX goes to Nail Brown! > > -- > Wilfried Weissmann ( mailto:[EMAIL PROTECTED] ) > Mobile: +43 676 965 > Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.3 VFS bug and namei.c bug
dev 08:01 This is a SCSI device sorry... On Mon, 16 Apr 2001, Mickey Lalescu wrote: > I am not sure if this is an IDE problem it seems to be an VFS one but I > can't find the maintainer for VFS. Ouch while I was trying to submit this > other bug I've got another one. Here is the output of the new one > > I/O error: dev 08:01, sector 67080 > kernel BUG at namei.c:343! > invalid operand: > CPU:0 > EIP:0010:[] > EFLAGS: 00010282 > eax: 001b ebx: cb8efe68 ecx: c4de6000 edx: c02c7f68 > esi: c393a660 edi: cb8efea8 ebp: cb8efe0c esp: cb8efe00 > ds: 0018 es: 0018 ss: 0018 > Process man (pid: 415, stackpage=cb8ef000) > Stack: c0276e8b c0276f43 0157 005b 006c 0026b6ff 01f4 > >0003 cd02a3c0 c012fb40 c0276fee cb8efe68 cb8efea8 cf941bc0 > c01706ab >c393a660 cf941c20 0003 cb8efe68 cb8efea8 cd02a3c0 > c5ed5000 > Call Trace: [] [] [] [] [] > [] [] >[] [] > > Code: 0f 0b 83 c4 0c 8b 54 24 3c 52 8b 44 24 3c 50 57 55 e8 25 fc > Segmentation fault > > > I am also getting some reiserfs errors. I don't know if this is related with > the other two bugs. I coud not capture the text of this last error. > > > Mickey Lalescu, Application Architect > Personus (Toronto) > 36 Lombard Street., 3rd Floor, Toronto ON M5C 2X3 > TEL 416 941-9340 Ext. 134 FAX 416 941-9183 > EMAIL [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> WEB < > http://www.personus.com <http://www.personus.com/> > > > > 1 + 1 = 3 for huge values of 1 > > > Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: via udma100 fix
On Mon, 16 Apr 2001, Dan Hollis wrote:
> I don't know if anyone noticed, but the supposed udma100 fix has been
> posted here:
>
> http://www.viahardware.com/download/viatweak.shtm
>
> At the bottom of the page.
>
> Technical discussion of the workaround (in german):
> http://home.tiscalinet.de/au-ja/review-kt133a-4.html
>
> -Dan
Hi Dan,
This was sent to me the other day, is this waht you are talking about?
Cheers,
Andre Hedrick
Linux ATA Development
ASL Kernel Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035Web: www.aslab.com
--- linux-2.4.3/drivers/pci/quirks.c.kicker Sun Apr 15 20:38:42 2001
+++ linux-2.4.3/drivers/pci/quirks.cSun Apr 15 21:20:49 2001
@@ -85,6 +85,29 @@
}
/*
+ * VIA Apollo KT133 needs PCI latency patch
+ * Made according to a windows driver based patch by George E. Breese
+ * see PCI Latency Adjust on http://www.viahardware.com/download/viatweak.shtm
+ */
+static void __init quirk_vialatency(struct pci_dev *dev)
+{
+ u8 r70;
+
+ printk(KERN_INFO "Applying VIA PCI latency patch.\n");
+ /*
+*In register 0x70, mask off bit 2 (PCI Master read caching)
+*and 1 (Delay Transaction)
+*/
+ pci_read_config_byte(dev, 0x70, );
+ r70 &= 0xf9;
+ pci_write_config_byte(dev, 0x70, r70);
+ /*
+*Turn off PCI Latency timeout (set to 0 clocks)
+*/
+ pci_write_config_byte(dev, 0x75, 0x80);
+}
+
+/*
* VIA Apollo VP3 needs ETBF on BT848/878
*/
@@ -275,6 +298,7 @@
{ PCI_FIXUP_FINAL, PCI_VENDOR_ID_INTEL,PCI_DEVICE_ID_INTEL_82443BX_2,
quirk_natoma },
{ PCI_FIXUP_FINAL, PCI_VENDOR_ID_SI, PCI_DEVICE_ID_SI_5597,
quirk_nopcipci },
{ PCI_FIXUP_FINAL, PCI_VENDOR_ID_SI, PCI_DEVICE_ID_SI_496,
quirk_nopcipci },
+ { PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_8363_0,
+ quirk_vialatency },
{ PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C597_0,
quirk_viaetbf },
{ PCI_FIXUP_HEADER, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C597_0,
quirk_vt82c598_id },
{ PCI_FIXUP_HEADER, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C586_3,
quirk_vt82c586_acpi },
Re: via udma100 fix
On Mon, 16 Apr 2001, Dan Hollis wrote:
I don't know if anyone noticed, but the supposed udma100 fix has been
posted here:
http://www.viahardware.com/download/viatweak.shtm
At the bottom of the page.
Technical discussion of the workaround (in german):
http://home.tiscalinet.de/au-ja/review-kt133a-4.html
-Dan
Hi Dan,
This was sent to me the other day, is this waht you are talking about?
Cheers,
Andre Hedrick
Linux ATA Development
ASL Kernel Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035Web: www.aslab.com
--- linux-2.4.3/drivers/pci/quirks.c.kicker Sun Apr 15 20:38:42 2001
+++ linux-2.4.3/drivers/pci/quirks.cSun Apr 15 21:20:49 2001
@@ -85,6 +85,29 @@
}
/*
+ * VIA Apollo KT133 needs PCI latency patch
+ * Made according to a windows driver based patch by George E. Breese
+ * see PCI Latency Adjust on http://www.viahardware.com/download/viatweak.shtm
+ */
+static void __init quirk_vialatency(struct pci_dev *dev)
+{
+ u8 r70;
+
+ printk(KERN_INFO "Applying VIA PCI latency patch.\n");
+ /*
+*In register 0x70, mask off bit 2 (PCI Master read caching)
+*and 1 (Delay Transaction)
+*/
+ pci_read_config_byte(dev, 0x70, r70);
+ r70 = 0xf9;
+ pci_write_config_byte(dev, 0x70, r70);
+ /*
+*Turn off PCI Latency timeout (set to 0 clocks)
+*/
+ pci_write_config_byte(dev, 0x75, 0x80);
+}
+
+/*
* VIA Apollo VP3 needs ETBF on BT848/878
*/
@@ -275,6 +298,7 @@
{ PCI_FIXUP_FINAL, PCI_VENDOR_ID_INTEL,PCI_DEVICE_ID_INTEL_82443BX_2,
quirk_natoma },
{ PCI_FIXUP_FINAL, PCI_VENDOR_ID_SI, PCI_DEVICE_ID_SI_5597,
quirk_nopcipci },
{ PCI_FIXUP_FINAL, PCI_VENDOR_ID_SI, PCI_DEVICE_ID_SI_496,
quirk_nopcipci },
+ { PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_8363_0,
+ quirk_vialatency },
{ PCI_FIXUP_FINAL, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C597_0,
quirk_viaetbf },
{ PCI_FIXUP_HEADER, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C597_0,
quirk_vt82c598_id },
{ PCI_FIXUP_HEADER, PCI_VENDOR_ID_VIA, PCI_DEVICE_ID_VIA_82C586_3,
quirk_vt82c586_acpi },
Re: 2.4.3 VFS bug and namei.c bug
dev 08:01 This is a SCSI device sorry... On Mon, 16 Apr 2001, Mickey Lalescu wrote: I am not sure if this is an IDE problem it seems to be an VFS one but I can't find the maintainer for VFS. Ouch while I was trying to submit this other bug I've got another one. Here is the output of the new one I/O error: dev 08:01, sector 67080 kernel BUG at namei.c:343! invalid operand: CPU:0 EIP:0010:[c0170585] EFLAGS: 00010282 eax: 001b ebx: cb8efe68 ecx: c4de6000 edx: c02c7f68 esi: c393a660 edi: cb8efea8 ebp: cb8efe0c esp: cb8efe00 ds: 0018 es: 0018 ss: 0018 Process man (pid: 415, stackpage=cb8ef000) Stack: c0276e8b c0276f43 0157 005b 006c 0026b6ff 01f4 0003 cd02a3c0 c012fb40 c0276fee cb8efe68 cb8efea8 cf941bc0 c01706ab c393a660 cf941c20 0003 cb8efe68 cb8efea8 cd02a3c0 c5ed5000 Call Trace: [c012fb40] [c01706ab] [c0140986] [c0138b6f] [c013930d] [c013995a] [c0136863] [c0107044] [c0106f27] Code: 0f 0b 83 c4 0c 8b 54 24 3c 52 8b 44 24 3c 50 57 55 e8 25 fc Segmentation fault I am also getting some reiserfs errors. I don't know if this is related with the other two bugs. I coud not capture the text of this last error. Mickey Lalescu, Application Architect Personus (Toronto) 36 Lombard Street., 3rd Floor, Toronto ON M5C 2X3 TEL 416 941-9340 Ext. 134 FAX 416 941-9183 EMAIL [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] WEB http://www.personus.com http://www.personus.com/ 1 + 1 = 3 for huge values of 1 Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Help with Fasttrack/100 Raid on Linux
Wilfried, Why a module? Why not have the detection and flags that hook the md driver for linux and use linux's software raid? Cheers, On Mon, 16 Apr 2001, Wilfried Weissmann wrote: Arjan van de Ven wrote: In article [EMAIL PROTECTED] you wrote: Andre Hedrick wrote: However as far as I can see everyone who has a FastTrak which is "stuck" in RAID mode[1] would be happy if it worked as a normal IDE controller in Linux, which is (usually?) not the case - eg on the MSI board where only the first channel is seen. I have a patch to work around that. However the better solution would be to have a native driver for the raid; I plan to start working on that next week... I am doing the same for the HighPoint-Tech 370 (talking about the RAID driver). Disk-striping is working so far. My code is based on the kernel patches for MDs from Neil Brown. I created an own RAID-personality for the module. When I looked at the FreeBSD implementation I had the idea of making a "supermodule" which could contain serveral IDE-RAID drivers (e.g.: Proise FastTrack + HPT370). There would be a super personality for ATA-RAID and several low-level drivers for the individual controllers. Interrested? Ideas? Hints, Tips, ...? Wanna team up? 8) Greetings, Arjan van de Ven regards, Wilfried PS: An uppercase THANX goes to Nail Brown! -- Wilfried Weissmann ( mailto:[EMAIL PROTECTED] ) Mobile: +43 676 9444465 Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-Kernel Archive: No 100 HZ timer !
On Thu, 12 Apr 2001, george anzinger wrote: > Actually we could do the same thing they did for errno, i.e. > > #define jiffies get_jiffies() > extern unsigned get_jiffies(void); > No, not really. HZ still defines the units of jiffies and most all the > timing is still related to it. Its just that interrupts are only "set > up" when a "real" time event is due. Great HZ always defines units of jiffies, but that is worthless if there is not a ruleset that tells me a value to divide by to return it to a specific quantity of time. Cheers, Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Help with Fasttrack/100 Raid on Linux
Stephen, Just telling me this fact is preaching to the choir, you have to express this on the mailing list, so others can hear first hand that you dislike the product and their support is non-existant. You will get no support for kernels that are not precompiled with distros, that will be a fact. They have ne desire or intention to support linux. Instead of accepting help, the patronize. The insult the global linux community with phrases like: 'we are more concerned with quality and compatablity, than to runs to market...' Yet they have yet to follow the programming rules of modules, including the basics of spinlocks/semephores/queue-locks. So great icon of compatablity with the other os, is vaporware. You should not trust that their driver will protect you other OS if you access under Linux. I expect it to eat and damage it just like you are seeing you Linux partitions being eaten. Sorry, but http://www.linux-ide.org/ clearly states that nothing below a given line supports hardware/bios-soft raid. Regards, Andre Hedrick Linux ATA Development On Thu, 12 Apr 2001, Stephen Woodbridge wrote: > Andre, > > Thank you for your quick response. I was afraid that was going to be the > situation. They have not been much help. I guess I will just buy another > regular ATA/100 controller and use software RAID. I wish I had know this > before I spent the money on the FastTrack100 controller. > > Best regards, > -Steve > > Andre Hedrick wrote: > > > > Stephen, > > > > Sorry but that is a closed source driver and you have to goto Promise, LOL. > > Last time I talked to them they sent me an email virus that choked a drive. > > Scan your mail first and then count your fingers if you have to shake > > hands with somebody their > > > > Andre Hedrick > > Linux ATA Development > > > > On Thu, 12 Apr 2001, Stephen Woodbridge wrote: > > > > > Andre, > > > > > > I have searched everywhere for some help getting my Promise > > > FrastTrack/100 Raid controller working. I finally found the ft.o driver > > > on the Promise website and have gotten it installed correctly (I think), > > > but I can NOT get fdisk to recognize the drive. Any help would be > > > greatly appreciated. > > > > > > Best regards, > > > -Stephen Woodbridge > > > > > > Here is what I have done so far: > > > > > > RedHat 6.2 > > > Linux 2.2.18 > > > (No other scsi devices in system) > > > > > > I added to /etc/conf.modules > > > alias block-major-8 ft > > > and copied the ft.o to /lib/modules/2.2.18/scsi > > > and did the depmod -a > > > and rebooted > > > > > > (after boot) ... > > > [root@linus /root]# lsmod > > > Module Size Used by > > > lockd 44688 0 (autoclean) (unused) > > > sunrpc 58820 0 (autoclean) [lockd] > > > 3c509 5996 1 (autoclean) > > > tulip 31888 1 (autoclean) > > > es1371 25920 0 > > > soundcore 2596 4 [es1371] > > > > > > [root@linus /root]# fdisk /dev/sda# tried repeatedly > > > > > > Unable to open /dev/sda > > > > > > [root@linus /root]# lsmod > > > Module Size Used by > > > ft 71048 0 (autoclean) (unused) > > > scsi_mod 38372 1 (autoclean) [ft] > > > lockd 44688 0 (autoclean) (unused) > > > sunrpc 58820 0 (autoclean) [lockd] > > > 3c509 5996 1 (autoclean) > > > tulip 31888 1 (autoclean) > > > es1371 25920 0 > > > soundcore 2596 4 [es1371] > > > [root@linus /root]# > > > > > > When fdisk tried to access /dev/sda the module was loaded and the > > > following banner shows up on the console: > > > > > > TastTrack Driver v1.10 build 3 (06.OCT.2000) > > > scsi0 : FASTTRACK > > > scsi : 1 host > > > Vendor: Promise Model: 1x2 Mirror/RAID1 Rev 1.10 > > > Type: Direct-Access ANSI SCSI revision: 02 > > > Vendor: Promise Model: 1x2 Mirror/RAID1 Rev 1.10 > > > Type: Direct-Access ANSI SCSI revision: 02 > > > Vendor: Promise Model: 1x2 Mirror/RAID1 Rev 1.10 > > > Type: Direct-Access ANSI SCSI revision: 02 > > > Vendor: Promise Model: 1x2 Mirror/RAID1 Rev 1.10 > > > Type: Direct-Access ANSI SCSI revision: 02 > > > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-Kernel Archive: No 100 HZ timer !
On Fri, 13 Apr 2001, Alan Cox wrote:
> > Okay but what will be used for a base for hardware that has critical
> > timing issues due to the rules of the hardware?
>
> > #define WAIT_MIN_SLEEP (2*HZ/100) /* 20msec - minimum sleep time */
> >
> > Give me something for HZ or a rule for getting a known base so I can have
> > your storage work and not corrupt.
>
>
> The same values would be valid with add_timer and friends regardless. Its just
> that people who do
>
> while(time_before(jiffies, started+DELAY))
> {
> if(poll_foo())
> break;
> }
>
> would need to either use add_timer or we could implement get_jiffies()
Okay regardless of the call what is it going to be or do we just random
and go oh-crap data!?!?
Since HZ!==100 of all archs that have ATA/ATAPI support, it is a mircale
that FS corruption and system death is not more rampant, except for the
fact that hardware is quick by a factor of 10+ so that 1000 does not quite
do as much harm but the associated mean of HZ changes and that is a
problem with slower hardware.
Nevermind just going nuts over the issues...
Just trying to keep the flamage down and stuff like that
Cheers,
Andre Hedrick
Linux ATA Development
ASL Kernel Development
-
ASL, Inc. Toll free: 1-877-ASL-3535
1757 Houret Court Fax: 1-408-941-2071
Milpitas, CA 95035Web: www.aslab.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Help with Fasttrack/100 Raid on Linux
Stephen, Sorry but that is a closed source driver and you have to goto Promise, LOL. Last time I talked to them they sent me an email virus that choked a drive. Scan your mail first and then count your fingers if you have to shake hands with somebody their Andre Hedrick Linux ATA Development On Thu, 12 Apr 2001, Stephen Woodbridge wrote: > Andre, > > I have searched everywhere for some help getting my Promise > FrastTrack/100 Raid controller working. I finally found the ft.o driver > on the Promise website and have gotten it installed correctly (I think), > but I can NOT get fdisk to recognize the drive. Any help would be > greatly appreciated. > > Best regards, > -Stephen Woodbridge > > Here is what I have done so far: > > RedHat 6.2 > Linux 2.2.18 > (No other scsi devices in system) > > I added to /etc/conf.modules > alias block-major-8 ft > and copied the ft.o to /lib/modules/2.2.18/scsi > and did the depmod -a > and rebooted > > (after boot) ... > [root@linus /root]# lsmod > Module Size Used by > lockd 44688 0 (autoclean) (unused) > sunrpc 58820 0 (autoclean) [lockd] > 3c509 5996 1 (autoclean) > tulip 31888 1 (autoclean) > es1371 25920 0 > soundcore 2596 4 [es1371] > > [root@linus /root]# fdisk /dev/sda# tried repeatedly > > Unable to open /dev/sda > > [root@linus /root]# lsmod > Module Size Used by > ft 71048 0 (autoclean) (unused) > scsi_mod 38372 1 (autoclean) [ft] > lockd 44688 0 (autoclean) (unused) > sunrpc 58820 0 (autoclean) [lockd] > 3c509 5996 1 (autoclean) > tulip 31888 1 (autoclean) > es1371 25920 0 > soundcore 2596 4 [es1371] > [root@linus /root]# > > When fdisk tried to access /dev/sda the module was loaded and the > following banner shows up on the console: > > TastTrack Driver v1.10 build 3 (06.OCT.2000) > scsi0 : FASTTRACK > scsi : 1 host > Vendor: Promise Model: 1x2 Mirror/RAID1 Rev 1.10 > Type: Direct-Access ANSI SCSI revision: 02 > Vendor: Promise Model: 1x2 Mirror/RAID1 Rev 1.10 > Type: Direct-Access ANSI SCSI revision: 02 > Vendor: Promise Model: 1x2 Mirror/RAID1 Rev 1.10 > Type: Direct-Access ANSI SCSI revision: 02 > Vendor: Promise Model: 1x2 Mirror/RAID1 Rev 1.10 > Type: Direct-Access ANSI SCSI revision: 02 > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ide.2.2.19.04092001.patch
On Thu, 12 Apr 2001, Shane Wegner wrote: > On Thu, Apr 12, 2001 at 03:05:53PM -0700, Andre Hedrick wrote: > > > > So you want a VIA-old and VIA-new ?? > > Hi, > > Is the version of the driver in the latest IDE patch v4.x? > That's odd as that driver does work fine on Linux 2.4.3. > It's just the one in 2.2.19+ide.2.2.19.0405 which seems to > be locking up. Not it is a migration to what is in Linux 2.4.3, but not there yet. This is a 3.x version. > Best regards, > Shane > > > > > On Tue, 10 Apr 2001, Shane Wegner wrote: > > > > > On Mon, Apr 09, 2001 at 05:33:13PM -0700, Andre Hedrick wrote: > > > > > > > > This is up with some updates > > > Hi, > > > > > > This isn't working here on my Abit VP6 board. The > > > ide.2.2.18.1221 works fine but this latest patch as well as > > > ide.2.2.19.0325 fails. > > > > > > Uniform Multi-Platform E-IDE driver Revision: 6.30 > > > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > > > VP_IDE: IDE controller on PCI bus 00 dev 39 > > > VP_IDE: chipset revision 6 > > > VP_IDE: not 100% native mode: will probe irqs later > > > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > > > VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1 > > > ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:pio > > > ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio > > > HPT370: IDE controller on PCI bus 00 dev 70 > > > HPT370: chipset revision 3 > > > HPT370: not 100% native mode: will probe irqs later > > > ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:pio, hdf:pio > > > ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:DMA, hdh:pio > > > hda: Maxtor 92720U8, ATA DISK drive > > > hdg: Maxtor 96147U8, ATA DISK drive > > > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > > > ide3 at 0xe400-0xe407,0xe802 on irq 10 > > > > > > That's where it stops. Locks solid, not even sysrq-b > > > works. > > > > > > Shane > > > > > > -- > > > Shane Wegner: [EMAIL PROTECTED] > > > http://www.cm.nu/~shane/ > > > PGP: 1024D/FFE3035D > > > A0ED DAC4 77EC D674 5487 > > > 5B5C 4F89 9A4E FFE3 035D > > > > > > > Andre Hedrick > > Linux ATA Development > > ASL Kernel Development > > --------- > > ASL, Inc. Toll free: 1-877-ASL-3535 > > 1757 Houret Court Fax: 1-408-941-2071 > > Milpitas, CA 95035Web: www.aslab.com > > -- > Shane Wegner: [EMAIL PROTECTED] > http://www.cm.nu/~shane/ > PGP: 1024D/FFE3035D > A0ED DAC4 77EC D674 5487 > 5B5C 4F89 9A4E FFE3 035D > Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ide.2.2.19.04092001.patch
So you want a VIA-old and VIA-new ?? On Tue, 10 Apr 2001, Shane Wegner wrote: > On Mon, Apr 09, 2001 at 05:33:13PM -0700, Andre Hedrick wrote: > > > > This is up with some updates > Hi, > > This isn't working here on my Abit VP6 board. The > ide.2.2.18.1221 works fine but this latest patch as well as > ide.2.2.19.0325 fails. > > Uniform Multi-Platform E-IDE driver Revision: 6.30 > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > VP_IDE: IDE controller on PCI bus 00 dev 39 > VP_IDE: chipset revision 6 > VP_IDE: not 100% native mode: will probe irqs later > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1 > ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:pio > ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio > HPT370: IDE controller on PCI bus 00 dev 70 > HPT370: chipset revision 3 > HPT370: not 100% native mode: will probe irqs later > ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:pio, hdf:pio > ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:DMA, hdh:pio > hda: Maxtor 92720U8, ATA DISK drive > hdg: Maxtor 96147U8, ATA DISK drive > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > ide3 at 0xe400-0xe407,0xe802 on irq 10 > > That's where it stops. Locks solid, not even sysrq-b > works. > > Shane > > -- > Shane Wegner: [EMAIL PROTECTED] > http://www.cm.nu/~shane/ > PGP: 1024D/FFE3035D > A0ED DAC4 77EC D674 5487 > 5B5C 4F89 9A4E FFE3 035D > Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: (ide.2.2.19.04092001.patch:) DiskPerf compile problem
http://www.xx.kernel.org/pub/linux/kernel/people/hedrick/utility-patches/DiskPerf-1.0.4.tar.gz http://www.xx.kernel.org/pub/linux/kernel/people/hedrick/utility-patches/DiskPerf-1.0.4.tar.bz2 Cheers, Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-Kernel Archive: No 100 HZ timer !
Okay but what will be used for a base for hardware that has critical timing issues due to the rules of the hardware? I do not care but your drives/floppy/tapes/cdroms/cdrws do: /* * Timeouts for various operations: */ #define WAIT_DRQ(5*HZ/100) /* 50msec - spec allows up to 20ms */ #ifdef CONFIG_APM #define WAIT_READY (5*HZ) /* 5sec - some laptops are very slow */ #else #define WAIT_READY (3*HZ/100) /* 30msec - should be instantaneous */ #endif /* CONFIG_APM */ #define WAIT_PIDENTIFY (10*HZ) /* 10sec - should be less than 3ms (?), if all ATAPI CD is closed at boot */ #define WAIT_WORSTCASE (30*HZ) /* 30sec - worst case when spinning up */ #define WAIT_CMD(10*HZ) /* 10sec - maximum wait for an IRQ to happen */ #define WAIT_MIN_SLEEP (2*HZ/100) /* 20msec - minimum sleep time */ Give me something for HZ or a rule for getting a known base so I can have your storage work and not corrupt. Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Linux-Kernel Archive: No 100 HZ timer !
Okay but what will be used for a base for hardware that has critical timing issues due to the rules of the hardware? I do not care but your drives/floppy/tapes/cdroms/cdrws do: /* * Timeouts for various operations: */ #define WAIT_DRQ(5*HZ/100) /* 50msec - spec allows up to 20ms */ #ifdef CONFIG_APM #define WAIT_READY (5*HZ) /* 5sec - some laptops are very slow */ #else #define WAIT_READY (3*HZ/100) /* 30msec - should be instantaneous */ #endif /* CONFIG_APM */ #define WAIT_PIDENTIFY (10*HZ) /* 10sec - should be less than 3ms (?), if all ATAPI CD is closed at boot */ #define WAIT_WORSTCASE (30*HZ) /* 30sec - worst case when spinning up */ #define WAIT_CMD(10*HZ) /* 10sec - maximum wait for an IRQ to happen */ #define WAIT_MIN_SLEEP (2*HZ/100) /* 20msec - minimum sleep time */ Give me something for HZ or a rule for getting a known base so I can have your storage work and not corrupt. Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: (ide.2.2.19.04092001.patch:) DiskPerf compile problem
http://www.xx.kernel.org/pub/linux/kernel/people/hedrick/utility-patches/DiskPerf-1.0.4.tar.gz http://www.xx.kernel.org/pub/linux/kernel/people/hedrick/utility-patches/DiskPerf-1.0.4.tar.bz2 Cheers, Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ide.2.2.19.04092001.patch
So you want a VIA-old and VIA-new ?? On Tue, 10 Apr 2001, Shane Wegner wrote: On Mon, Apr 09, 2001 at 05:33:13PM -0700, Andre Hedrick wrote: This is up with some updates Hi, This isn't working here on my Abit VP6 board. The ide.2.2.18.1221 works fine but this latest patch as well as ide.2.2.19.0325 fails. Uniform Multi-Platform E-IDE driver Revision: 6.30 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller on PCI bus 00 dev 39 VP_IDE: chipset revision 6 VP_IDE: not 100% native mode: will probe irqs later ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1 ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio HPT370: IDE controller on PCI bus 00 dev 70 HPT370: chipset revision 3 HPT370: not 100% native mode: will probe irqs later ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:pio, hdf:pio ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:DMA, hdh:pio hda: Maxtor 92720U8, ATA DISK drive hdg: Maxtor 96147U8, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide3 at 0xe400-0xe407,0xe802 on irq 10 That's where it stops. Locks solid, not even sysrq-b works. Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ide.2.2.19.04092001.patch
On Thu, 12 Apr 2001, Shane Wegner wrote: On Thu, Apr 12, 2001 at 03:05:53PM -0700, Andre Hedrick wrote: So you want a VIA-old and VIA-new ?? Hi, Is the version of the driver in the latest IDE patch v4.x? That's odd as that driver does work fine on Linux 2.4.3. It's just the one in 2.2.19+ide.2.2.19.0405 which seems to be locking up. Not it is a migration to what is in Linux 2.4.3, but not there yet. This is a 3.x version. Best regards, Shane On Tue, 10 Apr 2001, Shane Wegner wrote: On Mon, Apr 09, 2001 at 05:33:13PM -0700, Andre Hedrick wrote: This is up with some updates Hi, This isn't working here on my Abit VP6 board. The ide.2.2.18.1221 works fine but this latest patch as well as ide.2.2.19.0325 fails. Uniform Multi-Platform E-IDE driver Revision: 6.30 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: IDE controller on PCI bus 00 dev 39 VP_IDE: chipset revision 6 VP_IDE: not 100% native mode: will probe irqs later ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1 ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio HPT370: IDE controller on PCI bus 00 dev 70 HPT370: chipset revision 3 HPT370: not 100% native mode: will probe irqs later ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:pio, hdf:pio ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:DMA, hdh:pio hda: Maxtor 92720U8, ATA DISK drive hdg: Maxtor 96147U8, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide3 at 0xe400-0xe407,0xe802 on irq 10 That's where it stops. Locks solid, not even sysrq-b works. Shane -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com -- Shane Wegner: [EMAIL PROTECTED] http://www.cm.nu/~shane/ PGP: 1024D/FFE3035D A0ED DAC4 77EC D674 5487 5B5C 4F89 9A4E FFE3 035D Andre Hedrick Linux ATA Development ASL Kernel Development - ASL, Inc. Toll free: 1-877-ASL-3535 1757 Houret Court Fax: 1-408-941-2071 Milpitas, CA 95035Web: www.aslab.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
