Re: 3c905c support needed for etherboot

[Steve_Marfisi@3com.com]

>>Steve, do you know if 3com permanently write-protected the bootblock of
>>the at49bv512 on the 3c905c-tx-m?

We did it on the 905b (prevented corruption of the ROM because of early faulty
USB devices). The 905c is not write protected.

>>It would also be very interesting to find out how easily the ROM image
>>on the 3c905c-tx-m would interoperate with an Etherboot type of environment,
>>or whether the protocols used are more proprietary in nature.

Not sure about interoperability with Etherboot - but our protocol support is
absolutely not proprietary. Our BOOTP / DHCP / PXE code adheres to and answers
most RFC-compliant boot servers that we are aware of , tested on VAX, vmWorks,
QNX, four different Linuxes, AIX, HP UX, Solaris, Unixware, NT, NetWare (they do
bootp / tftp with their NFS add-on), OS/2.

Steve




Greg Beeley <Greg.Beeley@LightSys.org> on 01/11/2000 11:01:49 AM

Please respond to netboot@baghira.han.de

To:   netboot@baghira.han.de
cc:    (bcc: Steve Marfisi/US/3Com)

Subject:  Re: 3c905c support needed for etherboot





Ken Yap wrote:
> >What is needed to make the 3c905c etherbootable? Given that there is linux
> >driver source, I would think it wouldn't be too hard...
>
> Some hacking and lots of testing. I think Greg Beeley is looking into it.

3com said they were shipping the 3c905c documentation to me.  As soon as I
get that documentation I'll be able to have a fairly good idea regarding
the scope of the project.  If someone else who actually has a 3c905c
would like to write the updated driver, that would be great also as I
don't know at what point we'll actually need to purchase more network
computers (and thus probably start using 3c905c instead of 3c905b).  But
nevertheless I'm hoping to be able to give anyone who is interested a
good idea of what needs to be done to make it work, or do it myself when
the time comes (which may not be as soon as some of you all might need).

The 3c905b and 3c905 were very similar, excepting some added capabilities
and register variations for the 'b'.  If the 'c' is as similar to the 'b'
as the 'b' was to the 3c905, it shouldn't be a hard project -- maybe a
day's worth of reading docs, a day's worth of coding, and then plenty of
testing.  That's if there are no strange issues to work around like that
"MII ROM mapping bug" in the 3c905b :)

Steve, do you know if 3com permanently write-protected the bootblock of
the at49bv512 on the 3c905c-tx-m?

It would also be very interesting to find out how easily the ROM image
on the 3c905c-tx-m would interoperate with an Etherboot type of environment,
or whether the protocols used are more proprietary in nature.

Greg.

------------------------------------------------------------------------
Greg.Beeley@LightSys.org        LightSys - Redeeming Technology...
http://www.LightSys.org                    For God's Kingdom.
------------------------------------------------------------------------
===========================================================================
This Mail was sent to netboot mailing list by:
Greg Beeley <Greg.Beeley@LightSys.org>
To get help about this list, send a mail with 'help' as the only string in
it's body to majordomo@baghira.han.de. If you have problems with this list,
send a mail to netboot-owner@baghira.han.de.







===========================================================================
This Mail was sent to netboot mailing list by:
Steve_Marfisi@3com.com
To get help about this list, send a mail with 'help' as the only string in
it's body to majordomo@baghira.han.de. If you have problems with this list,
send a mail to netboot-owner@baghira.han.de.