How to create Fedora Core 1 driver disks? (rehash of previous iteraid question)

[Paul Gear]

Hi all,

I'm trying to use Doug Ledford's driver disk package
(http://people.redhat.com/dledford/) to create a driver disk for the ITE
RAID driver, and i'm missing something.  I hacked the makefile to give
me a directory for FC1, but it doesn't produce the correct result.

Some things that were not clear to me from the doco:

1.  Should the entire kernel tree be present at 2.4.22-1.2115.nptl/ in
the directory where the kit is extracted?  It seems that something is
required here, but my copy of the source from
/usr/src/linux-2.4.22-1.2115.nptl/ didn't seem to produce the correct
result.

2.  Should the Makefile in scsi/ just make the driver i'm interested in,
or must it be for a full build tree with additional patches for the
driver i'm making?

3.  What should the contents of scsi/ be?  It seems that at least some
of the files need to be named differently from their names on the final
driver disk (e.g. module-info vs. modinfo, rhdd-6.1 vs. disk-info), but
i can't work out which ones need to be named which.

4.  Some of the files in my scsi/ directory seemed to get copied and/or
linked into 2.4.22-1.2115.nptl/.  Is this normal, or am i doing
something else wrong?

Thanks in advance for your replies.

-- 
Paul
http://paulgear.webhop.net
-- 
A: Because we read from top to bottom, left to right.
Q: Why should i start my email reply *below* the quoted text?

[Paul Gear]

Paul Gear wrote:
>  Hi all,
>  
>  I'm trying to use Doug Ledford's driver disk package
>  (http://people.redhat.com/dledford/) to create a driver disk for the ITE
>  RAID driver, and i'm missing something.  I hacked the makefile to give
>  me a directory for FC1, but it doesn't produce the correct result.
>  
>  Some things that were not clear to me from the doco:
>  
>  1.  Should the entire kernel tree be present at 2.4.22-1.2115.nptl/ in
>  the directory where the kit is extracted?  It seems that something is
>  required here, but my copy of the source from
>  /usr/src/linux-2.4.22-1.2115.nptl/ didn't seem to produce the correct
>  result.
>  
>  2.  Should the Makefile in scsi/ just make the driver i'm interested in,
>  or must it be for a full build tree with additional patches for the
>  driver i'm making?
>  
>  3.  What should the contents of scsi/ be?  It seems that at least some
>  of the files need to be named differently from their names on the final
>  driver disk (e.g. module-info vs. modinfo, rhdd-6.1 vs. disk-info), but
>  i can't work out which ones need to be named which.
>  
>  4.  Some of the files in my scsi/ directory seemed to get copied and/or
>  linked into 2.4.22-1.2115.nptl/.  Is this normal, or am i doing
>  something else wrong?
>  
>  Thanks in advance for your replies. 
Apologies for pestering, but does anyone out there have the time to
answer these few questions?

-- 
Paul
http://paulgear.webhop.net
-- 
A: Because we read from top to bottom, left to right.
Q: Why should i start my email reply *below* the quoted text?

[David Kewley]

Paul Gear wrote on Wednesday 24 March 2004 01:55:
>  Paul Gear wrote:
>  > Hi all,
>  > 
>  > I'm trying to use Doug Ledford's driver disk package
>  > (http://people.redhat.com/dledford/) to create a driver disk for the ITE
>  > RAID driver, and i'm missing something.  I hacked the makefile to give
>  > me a directory for FC1, but it doesn't produce the correct result.
>  > 
>  > Some things that were not clear to me from the doco:
>  > 
>  > 1.  Should the entire kernel tree be present at 2.4.22-1.2115.nptl/ in
>  > the directory where the kit is extracted?  It seems that something is
>  > required here, but my copy of the source from
>  > /usr/src/linux-2.4.22-1.2115.nptl/ didn't seem to produce the correct
>  > result.
>  > 
>  > 2.  Should the Makefile in scsi/ just make the driver i'm interested in,
>  > or must it be for a full build tree with additional patches for the
>  > driver i'm making?
>  > 
>  > 3.  What should the contents of scsi/ be?  It seems that at least some
>  > of the files need to be named differently from their names on the final
>  > driver disk (e.g. module-info vs. modinfo, rhdd-6.1 vs. disk-info), but
>  > i can't work out which ones need to be named which.
>  > 
>  > 4.  Some of the files in my scsi/ directory seemed to get copied and/or
>  > linked into 2.4.22-1.2115.nptl/.  Is this normal, or am i doing
>  > something else wrong?
>  > 
>  > Thanks in advance for your replies.
>  
>  Apologies for pestering, but does anyone out there have the time to
>  answer these few questions? 
Paul,

I haven't made FC driver disks yet, but I wrote up the process I used (using 
Doug Ledford's kit) to make driver disks for RHL 9.  See:

http://www.klab.caltech.edu/~kewley/driverdisk/dd.html

I'd be interested to hear if this works for you, or if you run into any 
further problems.

BTW, sorry for the few-days delay; I just now read the request you made on 
Saturday. :)

David