archive mirror
 help / color / mirror / Atom feed
From: Doug Ledford <>
To: Steven Cole <>
Cc: backblue <>,
	Alan Cox <>,
Subject: Re: Error compiling, scsi 2.6.0-test1
Date: Thu, 24 Jul 2003 03:51:50 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Steven Cole wrote:
> On Thu, 2003-07-17 at 12:59, backblue wrote:
>>hello Alan,
>>I need this driver, but i dont know anouth of C, to code a new one, that old's on 2.6.0 :(, where to start? i really need it, i have everything scsi on my computer, with this controler, and i dont like the idea, of dont have suport to it!!
>>On 17 Jul 2003 12:51:42 +0100
>>Alan Cox <> wrote:
>>>On Mer, 2003-07-16 at 23:28, backblue wrote:
>>>>I have gcc 3.3, on x86 machine, i have this error, compiling the suport for my scsi card, someone know the problem?
>>>Nobody has coverted this driver to 2.6 yet. If someone does then it will
>>>get merged in, if not the initio support will get deleted in time.
> It looks like this came up a year ago:
> You might plead with Doug to finish the conversion.
> Steven

I wretched horribly when I read that driver.  Then I started to renounce 
my computer ways to become a Tibetten Monk and live out the remainder of 
my days in peace and solice.  Unfortunately, about that time, a space 
thread passed another thread, opened up a short lived wormhole, and I 
got a futuristic glimpse of myself in a robe and bald and I immediately 
came back to my senses.  I still couldn't handle that driver code 
though.  The urge to fix massive brokenness other than just PCI DMA code 
issues was overwhelming to my right hand's obsessive/compulsive disorder.

However, as a hint to anyone out there, I fixed the other initio driver 
a long ways back.  A person could pull those 3 (I think) changesets from 
the kernel tree and see what I did.  If you ignore all the changes to 
eliminate the fixed array of hosts and that kind of crap, and just 
concentrate on the changes that involve the PCI DMA mapping, they should 
apply almost perfectly into this other initio driver as they are very 
close copies of each other.

   Doug Ledford <>     919-754-3700 x44233
            Red Hat, Inc.
            1801 Varsity Dr.
            Raleigh, NC 27606

  reply	other threads:[~2003-07-24  7:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14 20:19 Alan Shih: "TCP IP Offloading Interface" David griego
2003-07-14 20:31 ` Alan Shih
2003-07-16 22:28   ` Error compiling, scsi 2.6.0-test1 backblue
2003-07-16 23:09     ` Rahul Karnik
2003-07-17 11:51     ` Alan Cox
2003-07-17 18:59       ` backblue
2003-07-18 16:14         ` Joshua Schmidlkofer
2003-07-18 17:00         ` Steven Cole
2003-07-24  7:51           ` Doug Ledford [this message]
2003-07-14 20:34 ` Alan Shih: "TCP IP Offloading Interface" Alan Cox
2003-07-14 21:53   ` Deepak Saxena
2003-07-17 22:31     ` Bill Davidsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).