etherboot-developers — Discussion of developer issues

Re: [Etherboot-developers] NIC file and ROM images

[<ebi...@ln...>]

ke...@us... (Ken Yap) writes:

> Perl doesn't cover all applications, but it's perfectly adequate in many
> places where you't think only C will do the job, e.g. mknbi which does
> binary manipulations and a streaming video server. It may be a long time
> before we see an Etherboot in Perl though.

I guess my point is mknbi is just at the edge.  And I crossed that
edge with my version and wasn't at all happy about it.  Which is why
I advised caution.
 
> >What is clear is that you can have multiple rom images, with their
> >own rom header on a 512 byte boundary.  What I don't know yet is
> >if the rom scan algorithm supports those images overlapping.
> 
> I don't think the header has any "data offset" fields, the body just
> follows the header.

The structure is:

A.2  PnP Option ROM Header
Offset    Size     Value    Description
-----------------------------------------------------
00h       BYTE     55h       Signature byte 1.
01h       BYTE     AAh       Signature byte 2.
02h       BYTE     Varies    Option ROM length in 512-byte blocks.
03h       4 BYTES  Varies    Initialization entry point.
07h       17 BYTES Varies    Reserved.
18h       WORD     Varies    Offset to PCI data structure.
1Ah       WORD     Varies    Offset to expansion header structure.

So my question is, can we have something like:

PnP option ROM Header size 64K
512 bytes later, PnP option ROM Header size 64K - 512 bytes
512 bytes later, PnP option ROM header size 64K - 1024 bytes.
etc.

And just adjust the pointers to the code approrpiately.

> >If they can overlap it is probably worth doing, without the ability
> >to overlap we can just make certain etherboot rom images are in
> >multiples of 512 bytes and concat rom images together if there are
> >big enough roms.
> 
> That's easy, just concatenate the ROM images. At the moment they aren't
> as small as they could be because they are padded out to the next power
> of 2, but an additional option could allow them to be padded to the next
> block only.

Right concatenation will work, but you probably can't fit very
many of them into the same rom.  Which generally defeats the purpose.

If I have a chance I will see if I can get overlapping ROMs to work,
that way we can list all of the the supported PCI for one ROM image.

Eric

Re: [Etherboot-developers] NIC file and ROM images

[<ja...@Mc...>]

Interesting thread about the multiple PCI headers in a
bootrom.

I realize this would take alot of reworking how an
Etherboot bootrom image is put together, but I'm thinking
that much of the code in bootrom is common code that
is used in all bootroms.  That is, the tftp, dhcp/bootp,
main, and probably more.

Concatenating the bootrom images would just duplicate the
same code over and over again.

I don't know what the ratio of unique code to common code
is, but it seems like it is far more common code than unique.

What if you (we) could build a bootrom that knows about ALL
pci network chipsets.

It would start with a whole bunch of 512 byte PCI headers.
Followed by the main() and other common code,  Then, the 
unique routines that each card needs. I don't know how big
that is, but it seems pretty small, per chipset.

I use 29ee512 chips for the Linksys and 3Com cards, 
I'll bet we could fit support for a lot of chipsets into 64k.

Well, it's just a random thought.

Thanks,

Jim McQuillan
ja...@Lt...


On Thu, 18 Apr 2002, Ken Yap wrote:

> >That wouldn't have worked because I wasn't using that checksum
> >algorightm.  Ever since playing with BASIC I'm alergic to using
> >programming languages where you must use the builtins to get
> >performance.
> 
> Well then the answer would have been one of the following:
> 
> Find a CPAN module that does what you want. E.g. there's a MD5 module.
> Write an extension in C.
> Don't use Perl
> 
> Perl doesn't cover all applications, but it's perfectly adequate in many
> places where you't think only C will do the job, e.g. mknbi which does
> binary manipulations and a streaming video server. It may be a long time
> before we see an Etherboot in Perl though.
> 
> >What is clear is that you can have multiple rom images, with their
> >own rom header on a 512 byte boundary.  What I don't know yet is
> >if the rom scan algorithm supports those images overlapping.
> 
> I don't think the header has any "data offset" fields, the body just
> follows the header.
> 
> >If they can overlap it is probably worth doing, without the ability
> >to overlap we can just make certain etherboot rom images are in
> >multiples of 512 bytes and concat rom images together if there are
> >big enough roms.
> 
> That's easy, just concatenate the ROM images. At the moment they aren't
> as small as they could be because they are padded out to the next power
> of 2, but an additional option could allow them to be padded to the next
> block only.
> 
> _______________________________________________
> Etherboot-developers mailing list
> Eth...@li...
> https://lists.sourceforge.net/lists/listinfo/etherboot-developers
> 

-- 

Re: [Etherboot-developers] NIC file and ROM images

[<ke...@us...>]

>That wouldn't have worked because I wasn't using that checksum
>algorightm.  Ever since playing with BASIC I'm alergic to using
>programming languages where you must use the builtins to get
>performance.

Well then the answer would have been one of the following:

Find a CPAN module that does what you want. E.g. there's a MD5 module.
Write an extension in C.
Don't use Perl

Perl doesn't cover all applications, but it's perfectly adequate in many
places where you't think only C will do the job, e.g. mknbi which does
binary manipulations and a streaming video server. It may be a long time
before we see an Etherboot in Perl though.

>What is clear is that you can have multiple rom images, with their
>own rom header on a 512 byte boundary.  What I don't know yet is
>if the rom scan algorithm supports those images overlapping.

I don't think the header has any "data offset" fields, the body just
follows the header.

>If they can overlap it is probably worth doing, without the ability
>to overlap we can just make certain etherboot rom images are in
>multiples of 512 bytes and concat rom images together if there are
>big enough roms.

That's easy, just concatenate the ROM images. At the moment they aren't
as small as they could be because they are padded out to the next power
of 2, but an additional option could allow them to be padded to the next
block only.

Re: [Etherboot-developers] ISA 3C515 Driver

[<ke...@us...>]

>My sourceforge id is timlegge.  It is activated.

Ok, I'll sign you in.

>As for the all rights reserved, I must have copied that from another driver
>;-).  I can submit a patch to fix things.

Maybe cleaning up the code with indent wouldn't hurt, there is quite a
bit of old stuff lying around.

RE: [Etherboot-developers] ISA 3C515 Driver

[Timothy L. <tl...@ro...>]

Hi Ken

My sourceforge id is timlegge.  It is activated.

I contacted Donald today and he is fine with adding:

This driver includes code that is copyright 1997-2000 by Donald Becker.

And then the usual GPL notice and possibly a mention of how to contact him.

As for the all rights reserved, I must have copied that from another driver
;-).  I can submit a patch to fix things.

Tim



> -----Original Message-----
> From: eth...@li...
> [mailto:eth...@li...]On Behalf Of
> Ken Yap
> Sent: Wednesday, April 17, 2002 1:12 PM
> To: Etherboot developers list
> Subject: Re: [Etherboot-developers] ISA 3C515 Driver
>
>
> >This driver is a hack.  It seems to work, but I am not entirely sure how
> >I managed that.  However, I believe I would be correct in stating that
> >it is the best available 3c515 etherboot driver.  (Unless someone has
> >working driver for the 3c515 that I don't know of) ;-)
>
> And it probably is too. Thanks, added to source tree.
>
> BTW, you're asserted All Rights Reserved¸ is that compatible with the
> sources you've used, e.g. Donald Becker's driver, which is GPL?
>
> >Ken, I have registered with SourceForge, is there anything else I need
> >to do.
>
> Yes, tell me your id when it's activated. I can't find you in the people
> list so either you're registered under another name or the db is not up
> to date.
>
> _______________________________________________
> Etherboot-developers mailing list
> Eth...@li...
> https://lists.sourceforge.net/lists/listinfo/etherboot-developers
>

Re: [Etherboot-developers] NIC file and ROM images

[<ebi...@ln...>]

ke...@us... (Ken Yap) writes:

> >I'd be careful about using Perl for this kind of work.  I'm rather
> >turned off on Perl since I added code to compute a checksum and
> >Perl 5 seconds to checksum a 1Meg binary data.  That combined with the 
> >challenge of dealing with binary data in Perl causes me to suggest
> >that is is proabably  a more appropriate language for this task.
> 
> Relax, I know Perl like an old friend.  I bet you tried to sum each byte
> with a loop containing a substr.  Perl has a built-in for doing
> checksums, see unpack in perlfunc(1). Here's a quickie to verify that
> the a ROM image checksums to 0.

I did use substrings and that might have been the issue.
> 
> #!/usr/bin/perl
> $/ = 0777;
> $sum = unpack("%8C*",<>);
> print "$sum\n";

That wouldn't have worked because I wasn't using that checksum
algorightm.  Ever since playing with BASIC I'm alergic to using
programming languages where you must use the builtins to get
performance.

> >> The NIC file could also generate an include for config.c, so only one
> >> place needs to be changed to support another derived image.
> >
> >That might be a good idea.  But it falls down on the multiple drives
> >in one NIC side.  I would be in favor of all of the PCI ID moving into
> >the drivers so drivers can be independent.
> 
> But you haven't found out yet if an image can actually contain multiple
> PCI headers and do the right thing.

I have now.

What is clear is that you can have multiple rom images, with their
own rom header on a 512 byte boundary.  What I don't know yet is
if the rom scan algorithm supports those images overlapping.

If they can overlap it is probably worth doing, without the ability
to overlap we can just make certain etherboot rom images are in
multiples of 512 bytes and concat rom images together if there are
big enough roms.

Eric

Re: [Etherboot-developers] ISA 3C515 Driver

[Marty C. <md...@th...>]

On 4/17/2002 11:39 AM Timothy Legge tl...@ro... wrote:
>I have attached the driver for the 3c515 card.  
>...
>This driver is a hack.  It seems to work, but I am not entirely sure how 
>I managed that.  However, I believe I would be correct in stating that 
>it is the best available 3c515 etherboot driver.  (Unless someone has 
>working driver for the 3c515 that I don't know of) ;-)

You did a fine job.  Many people who you will never meet will appreciate 
your work.

Driver writing is a learning experience, like so many things in life.  
What you figured out from writing this driver will help you on your next 
one.

Many thanks for your good work.

Marty

---
    Try: http://rom-o-matic.net/ to make Etherboot images instantly.

   Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827; Cambridge, MA 02139; USA
  Voice: (617) 491-6935, Fax: (617) 491-7046 
  Email: md...@th...
    Web: http://www.thinguin.org/

Re: [Etherboot-developers] ISA 3C515 Driver

[<ke...@us...>]

>This driver is a hack.  It seems to work, but I am not entirely sure how 
>I managed that.  However, I believe I would be correct in stating that 
>it is the best available 3c515 etherboot driver.  (Unless someone has 
>working driver for the 3c515 that I don't know of) ;-)

And it probably is too. Thanks, added to source tree.

BTW, you're asserted All Rights Reserved¸ is that compatible with the
sources you've used, e.g. Donald Becker's driver, which is GPL?

>Ken, I have registered with SourceForge, is there anything else I need 
>to do.

Yes, tell me your id when it's activated. I can't find you in the people
list so either you're registered under another name or the db is not up
to date.

[Etherboot-developers] ISA 3C515 Driver

[Timothy L. <tl...@ro...>]

Hi

I have attached the driver for the 3c515 card.  

As far as I know, the driver only works with a PC with BIOS support for 
PNP.  I will test that on a 486 in the near future.  If it does not work 
on non PNP enabled BIOSes, I would welcome input on how to add the 
required features from the ISAPNP software.

There are a whole lot of defines that are probably unneeded.  I left 
them in in the initial release just in case the need to be used later to 
support other boards.  (OK, I was too lazy and excited to bother taking 
them out).

This driver is a hack.  It seems to work, but I am not entirely sure how 
I managed that.  However, I believe I would be correct in stating that 
it is the best available 3c515 etherboot driver.  (Unless someone has 
working driver for the 3c515 that I don't know of) ;-)

Ken, I have registered with SourceForge, is there anything else I need 
to do.

Regarrds

Tim Legge
Moncton, NB
Canada

[Etherboot-developers] Re: [Etherboot-users] Driver for 3Com 3c515 Fast EtherLink ISA

[<ke...@us...>]

>Well with a lot of reading, (including a tutorial on Bitwise operations) 
>and with the help of a whole lot of etherboot drivers, I have finally 
>created a working driver for the 3c515.  

Well done! Good on ya mate.

>Actually, it came as quite a surprise.  I left the room while waiting 
>for yet another reboot and when I returned, the ltsp kernel was booting 
>on screen.

I wish my software could write itself like that. :-)

>Also, since I draw heavily on Donald Becker's linux driver as well as 
>some of the other 3Com etherboot drivers I assume that I should detail 
>that at the beginning of the driver.  Is that correct?

Probably a good idea to give credit where it's due.

If it's small (<40kB) you could mail it to the Etherboot developers
list, or put it on your web/ftp server and post the URL, or if you wish
to be an Etherboot developer, register at Sourceforge, then tell me and
I'll add you to the developer list, then you can check it into CVS or
post in the patch area.

Again, nice job.

Re: [Etherboot-developers] Prism II (wireless) drivers

[Michael B. <mb...@fe...>]

On Wed, 17 Apr 2002, Ken Yap wrote:
> >All now in CVS, including the multi-driver ROM stuff.  All builds fine on
> >my system, if anyone hits compile errors with my code please let me know.
> Sorry Michael, I've redesigned the format of the NIC spec file so your
> diffs have not been propagated because I haven't thought up of a
> replacement syntax for your multi-driver build specs. Suggest something.
> Maybe a section like:
> multi
> name=driver1,driver2,driver3	PCI-IDs	Comment
> You will find the revamped genrules.pl and NIC in CVS now.

Will take a look and code something in (I like Perl).

Michael

Re: [Etherboot-developers] Prism II (wireless) drivers

[<ke...@us...>]

>All now in CVS, including the multi-driver ROM stuff.  All builds fine on
>my system, if anyone hits compile errors with my code please let me know.

Sorry Michael, I've redesigned the format of the NIC spec file so your
diffs have not been propagated because I haven't thought up of a
replacement syntax for your multi-driver build specs. Suggest something.
Maybe a section like:

multi
name=driver1,driver2,driver3	PCI-IDs	Comment

You will find the revamped genrules.pl and NIC in CVS now.

[Etherboot-developers] Problems with two identical gigabit adapters

[<Rob...@ra...>]

Hi List,

I am trying to get a new SBC to network boot. The current code mostly works
wonderfully well, many thanks to Christopher Li for 82544 Gigabit port.

My blade has two gigabit chips on it and I can get the stock code to boot
from the first NIC but it won't follow the boot order laid out by the BIOS
(Phoenix 4.0.6) and I can't get the PXE code to do anything.

Robert Cheetham

RadiSys Corporation
5959 Corporate Drive
Houston
TX 77546
713-541-8267
------------------------------------------------------------------------------------------------

Change is inevitable - except from a coke machine
------------------------------------------------------------------------------------------------

"This electronic message contains information which may be confidential,
privileged or otherwise protected from disclosure.  The information is
intended to be used solely by the named recipient(s).  If you are not a
named recipient, any review, disclosure, copying, distribution or use of
this transmission or its contents is prohibited.  If you have received this
transmission in error, please notify me immediately."

[Etherboot-developers] Welcome

[The S. R. <in...@bo...>]

______________________________________________________________
The Stock Refinery never sends unsolicited email. You have received this message because you registered with The Stock Refinery OR one of our carefully selected marketing partners. If you no longer wish to receive these offers, please follow the instructions at the bottom of this message.
______________________________________________________________


The Stock Refinery is pleased to announce that we have joined forces with Wall Street Stockwatch, of which you are a current member, to bring you the most up-to-date company profiles via e-mail.

The theme of The Stock Refinery is to direct our Members with investment to small and micro cap companies which are not widely followed. These are the types of Companies that have not yet shown up on the radar screens of Professional Wall Street Money Managers or on the front page of the Wall Street Journal. In order to be Profiled, the Company must have a unique and proprietary technology or business model which will lend itself to Wall Street attention down the road if Management is successful at executing its business plan. We only profile companies that we feel are trading at a level that offers our Members significant upside potential when positions are held for the longer term.
The Stock Refinery Newsletter is not published on a scheduled basis. We release issues based on our ability to seek out and locate companies with accurate information that we feel will generate the kind of returns our members are looking for.

If you do not wish to receive further exciting profiles from The Stock Refinery, simple click the link at the bottom of this email to be removed. You will also be able to unsubscribe on each and every newsletter you receive from The Stock Refinery.

Thank you and welcome aboard.

_____________________________________________________________________________
The preceding message was sent to you as an opt-in subscriber to The Stock Refinery.
If you wish to unsubscribe please follow this link: 
http://marketrefinery.3web45.com/optout.htm?message_id=4&e=e...@li...
_____________________________________________________________________________

Re: [Etherboot-developers] Error in elf make for website

[<ebi...@ln...>]

ke...@us... (Ken Yap) writes:

> >different systems. When I saw the new options for the cards, I decided
> >that I would try it, for the two that I am most familiar with, the
> >3C509, and the 3C905. For those two, it broke, as indicated. I have not
> 
> Looking at the Makefile and Roms file.
> 
> 3c509 (ISA) is not supported for LinuxBIOS, so there is no make target
> for it.
> 
> 3c905 (PCI) is supported for LinuxBIOS as Eric indicated. But the
> problem is that you (or the rom-o-matic script) should be asking for
> foo.ebi, not foo.elf.  foo.elf is not a valid make target.

Right 3c90x.elf (which is the generic driver) should work.
And since LinuxBIOS just starts etherboot it really doesn't matter
which variant you pick so long as you have a valid pairing.

generic driver -> elf
specific driver -> ebi

Eric

Re: [Etherboot-developers] Error in elf make for website

[<ke...@us...>]

>different systems. When I saw the new options for the cards, I decided
>that I would try it, for the two that I am most familiar with, the
>3C509, and the 3C905. For those two, it broke, as indicated. I have not

Looking at the Makefile and Roms file.

3c509 (ISA) is not supported for LinuxBIOS, so there is no make target
for it.

3c905 (PCI) is supported for LinuxBIOS as Eric indicated. But the
problem is that you (or the rom-o-matic script) should be asking for
foo.ebi, not foo.elf.  foo.elf is not a valid make target.

RE: [Etherboot-developers] Error in elf make for website

[Gregg C L. <dr...@wo...>]

Hello from Gregg C Levine
And let me elaborate. I use exclusively the 3COM 3C905 cards for all of
my PCI based systems. In fact I have two running here, right now. In two
different systems. When I saw the new options for the cards, I decided
that I would try it, for the two that I am most familiar with, the
3C509, and the 3C905. For those two, it broke, as indicated. I have not
tried it, for any of the others, as I am not qualified to comment on a
different card, then what I have here. But you asked a valid point, both
times.
-------------------
Gregg C Levine han...@wo...
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."=A0 Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )



> -----Original Message-----
> From: er...@DL... [mailto:er...@DL...] On
> Behalf Of Eric W. Biederman
> Sent: Sunday, April 14, 2002 11:39 AM
> To: Gregg C Levine
> Cc: EtherBoot Developers
> Subject: Re: [Etherboot-developers] Error in elf make for website
>=20
> "Gregg C Levine" <dr...@wo...> writes:
>=20
> > Hello from Gregg C Levine
> > Not really Eric. Just testing the site. I had an idea that it would
fail
> > like that. But I wanted to test it, and then to report it.
>=20
> Let me ask again.
>=20
> Were you testing to see if ISA NICs would work?
> PCI NICs do work, this includes most 3COM cards.
>=20
> Eric

Re: [Etherboot-developers] Error in elf make for website

[<ebi...@ln...>]

"Gregg C Levine" <dr...@wo...> writes:

> Hello from Gregg C Levine
> Not really Eric. Just testing the site. I had an idea that it would fail
> like that. But I wanted to test it, and then to report it.

Let me ask again.

Were you testing to see if ISA NICs would work?
PCI NICs do work, this includes most 3COM cards.

Eric

RE: [Etherboot-developers] Error in elf make for website

[Gregg C L. <dr...@wo...>]

Hello from Gregg C Levine
Not really Eric. Just testing the site. I had an idea that it would fail
like that. But I wanted to test it, and then to report it.
-------------------
Gregg C Levine han...@wo...
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."=A0 Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )



> -----Original Message-----
> From: er...@DL... [mailto:er...@DL...] On
> Behalf Of Eric W. Biederman
> Sent: Sunday, April 14, 2002 11:30 AM
> To: Gregg C Levine
> Cc: EtherBoot Developers
> Subject: Re: [Etherboot-developers] Error in elf make for website
>=20
> "Gregg C Levine" <dr...@wo...> writes:
>=20
> > Hello from Gregg C Levine
> > Problems with making elf bootable images for two 3COM cards, the
3C509,
> > and 3C905. I am placing here a cut & paste of the 3C509, and the
3C905
> >
> > 3c509 Build Failed
>=20
> Gregg are you really trying to build for an ISA NIC?
> If so, ISA NICs are not currently supported (oversight), and that
> is your problem.
>=20
> If not your problem is you selected the wrong NIC.  All PCI NICs
> should build with LinuxBIOS support, though they haven't all been
> tested.
>=20
> Eric

Re: [Etherboot-developers] Error in elf make for website

[<ebi...@ln...>]

"Gregg C Levine" <dr...@wo...> writes:

> Hello from Gregg C Levine
> Problems with making elf bootable images for two 3COM cards, the 3C509,
> and 3C905. I am placing here a cut & paste of the 3C509, and the 3C905
> 
> 3c509 Build Failed

Gregg are you really trying to build for an ISA NIC?
If so, ISA NICs are not currently supported (oversight), and that
is your problem.

If not your problem is you selected the wrong NIC.  All PCI NICs
should build with LinuxBIOS support, though they haven't all been
tested.

Eric

Re: [Etherboot-developers] Error in elf make for website

[<ebi...@ln...>]

Marty Connor <md...@th...> writes:

> On 4/13/2002 7:39 PM Gregg C Levine dr...@wo... wrote:
> >Hello from Gregg C Levine
> >Problems with making elf bootable images for two 3COM cards, the 3C509,
> >and 3C905. I am placing here a cut & paste of the 3C509, and the 3C905
> >make: *** No rule to make target `bin32/3c509.elf'.  Stop.
> >make: Leaving directory `/tmp/ROMQkGW5W'

> Gregg,  rom-o-matic.net supports what the underlying packages support.  
> The .elf and .ebi formats are almost experimental right now.  Perhaps I 
> should put an even stronger warning on those options.

Given that Gregg was trying to build for LinuxBIOS he was in the
target user group :)
 
> >Marty this happened for these particular cards. I am also going to see
> >if I can create a similar image for the LinuxBIOS project, for the 3c509
> >That too failed with much the same error. Since the folks at the project
> >have not announced support for those cards, it is my guess that is why
> >we are getting those failures, but since there are more 3COM cards out
> >there, then nearly every single brand made, except for Intel, they
> >should be.

The 3c90x driver works fine.  For the most part if there is a
configuration that works in normal etherboot there is a configuration
that builds and probably works under LinuxBIOS.  In a few rare cases
drivers make unwarranted assumptions but we have already solved the worst
of that.

> I don't think I can be of much help with this.  Perhaps you should 
> correspond with the folks on the LinuxBIOS mailing list and see what they 
> say.  

Hmm.  Looking a little further it appears I currently do not support
building ISA NICs under LinuxBIOS.  It shouldn't be hard to change
but this is definentily not a rom-o-matic bug except possibly for
making it clear.  This appears to be an oversight on my part. 

Eric

Re: [Etherboot-developers] Error in elf make for website

[Marty C. <md...@th...>]

On 4/13/2002 7:39 PM Gregg C Levine dr...@wo... wrote:
>Hello from Gregg C Levine
>Problems with making elf bootable images for two 3COM cards, the 3C509,
>and 3C905. I am placing here a cut & paste of the 3C509, and the 3C905
>make: *** No rule to make target `bin32/3c509.elf'.  Stop.
>make: Leaving directory `/tmp/ROMQkGW5W'

Gregg,  rom-o-matic.net supports what the underlying packages support.  
The .elf and .ebi formats are almost experimental right now.  Perhaps I 
should put an even stronger warning on those options.

>Marty this happened for these particular cards. I am also going to see
>if I can create a similar image for the LinuxBIOS project, for the 3c509
>That too failed with much the same error. Since the folks at the project
>have not announced support for those cards, it is my guess that is why
>we are getting those failures, but since there are more 3COM cards out
>there, then nearly every single brand made, except for Intel, they
>should be.

I don't think I can be of much help with this.  Perhaps you should 
correspond with the folks on the LinuxBIOS mailing list and see what they 
say.  

Marty

---
    Try: http://rom-o-matic.net/ to make Etherboot images instantly.

   Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827; Cambridge, MA 02139; USA
  Voice: (617) 491-6935, Fax: (617) 491-7046 
  Email: md...@th...
    Web: http://www.thinguin.org/

Re: [Etherboot-developers] Prism II (wireless) drivers

[Marty C. <md...@th...>]

On 4/14/2002 9:18 AM Markus Gutschke ma...@gu... wrote:
>Marty Connor wrote:
>> Hmmmm, wireless Etherbooting....
>> You know of course that this means we'll have to cart *even more* demo 
>> hardware to LinuxWorld Expo San Francisco in August.  
>> Drat!! :) :) :)
>I  might be able to help out with some of that. I have a DWL-650/550 (i.e. 
>PCMCIA card and a PCI adapter card), a laptop running Linux, and a wireless 
>access point. While I use all of these daily, I can probably do without 
>them for 
>the duration of the show. Since I am local, there is no need for you to 
>ship all 
>of this from Boston. Markus

Thanks for the offer, Markus!  The last LinuxWorld in New York was great, 
and I hope you can be in the booth in August again.  Registration for the 
.ORG Pavillion doesn't seem to have started yet, but I'll certainly try 
to get us in as soon as it does.

I was mostly joking about bringing more equipment.  I actually enjoy 
seeing how much demo stuff we can bring in two large suitcases and fit 
into the booth :)  I'll probably be shipping a lot ahead to the hotel 
this time, and then it's the matter of getting it to the Moscone.

We might even want two demo machines this show.  One wireless and one 
wired.  I just happen to have gotten another case, and will get some 
plexiglas to make another demo box for display.

If everything works out, it could be a really fun time.  Maybe we can 
even somehow tempt Ken and Eric into coming :)

Marty

---
    Try: http://rom-o-matic.net/ to make Etherboot images instantly.

   Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827; Cambridge, MA 02139; USA
  Voice: (617) 491-6935, Fax: (617) 491-7046 
  Email: md...@th...
    Web: http://www.thinguin.org/

Re: [Etherboot-developers] Prism II (wireless) drivers

[Markus G. <ma...@gu...>]

Marty Connor wrote:
> Hmmmm, wireless Etherbooting....
> You know of course that this means we'll have to cart *even more* demo 
> hardware to LinuxWorld Expo San Francisco in August.  
> Drat!! :) :) :)

I  might be able to help out with some of that. I have a DWL-650/550 (i.e. 
PCMCIA card and a PCI adapter card), a laptop running Linux, and a wireless 
access point. While I use all of these daily, I can probably do without them for 
the duration of the show. Since I am local, there is no need for you to ship all 
of this from Boston.


Markus

-- 
Markus Gutschke
3637 Fillmore Street #106
San Francisco, CA 94123-1600
+1-415-567-8449
ma...@gu...

[Etherboot-developers] Error in elf make for website

[Gregg C L. <dr...@wo...>]

Hello from Gregg C Levine
Problems with making elf bootable images for two 3COM cards, the 3C509,
and 3C905. I am placing here a cut & paste of the 3C509, and the 3C905

3c509 Build Failed

------------------------------------------------------------------------
--------
Build failed. Status =3D 2.=20

Following is the output from make:=20


make: Entering directory `/tmp/ROMQkGW5W'
make: *** No rule to make target `bin32/3c509.elf'.  Stop.
make: Leaving directory `/tmp/ROMQkGW5W'
Please let us know that this happened.
(That was for the 3c509 type image, the 3c905 next)

3c905c-tpo Build Failed

------------------------------------------------------------------------
--------
Build failed. Status =3D 2.=20

Following is the output from make:=20


make: Entering directory `/tmp/ROMPNClfs'
make: *** No rule to make target `bin32/3c905c-tpo.elf'.  Stop.
make: Leaving directory `/tmp/ROMPNClfs'
Please let us know that this happened.

Marty this happened for these particular cards. I am also going to see
if I can create a similar image for the LinuxBIOS project, for the 3c509
That too failed with much the same error. Since the folks at the project
have not announced support for those cards, it is my guess that is why
we are getting those failures, but since there are more 3COM cards out
there, then nearly every single brand made, except for Intel, they
should be.
-------------------
Gregg C Levine dr...@wo...
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."=A0 Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )