etherboot-developers

Re: [Etherboot-developers] boot1a.s hacked to take .z?img directly

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

>It boots a single NIC driver, but when given etherboot.zimg, it fails
>with a Rd err. It was trying to read 0x9B blocks. I don't know if this
>is a media error, or a limitation of the packet interrupt that boot1a.s
>calls.

Actually I think I know what it is.  I don't think the EDD packet
interrupt that boot1a calls can handle > 64kB transfers.

Re: [Etherboot-developers] boot1a.s hacked to take .z?img directly

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

>> Actually I think I know what it is.  I don't think the EDD packet
>> interrupt that boot1a calls can handle > 64kB transfers.
>
>Ah.  Being 16bit code that makes a lot of sense.
>And I suspect with a little care it is solvable with a little loop.

My brain hurtz after all that assembly. I'll take a stab at it when I
have recovered. :-)

Re: [Etherboot-developers] boot1a.s hacked to take .z?img directly

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

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

> >It boots a single NIC driver, but when given etherboot.zimg, it fails
> >with a Rd err. It was trying to read 0x9B blocks. I don't know if this
> >is a media error, or a limitation of the packet interrupt that boot1a.s
> >calls.
> 
> Actually I think I know what it is.  I don't think the EDD packet
> interrupt that boot1a calls can handle > 64kB transfers.

Ah.  Being 16bit code that makes a lot of sense.
And I suspect with a little care it is solvable with a little loop.

At least the strange failures are starting to make sense.

I think we are finally on the downhill path towards 5.2.

The only outstanding thing I have remaining on my todo list
is to enable multicast support in the rest of the drivers.

Eric