On Sat, 10 Jun 2000, Urban Widmark wrote:
> On Fri, 9 Jun 2000, Konrad Podloucky wrote:
>
[...]
> Except for the zero length, that the driver doesn't attempt to handle it,
> that the driver tried to set up the card not to use more than one
> descriptor per frame, it doesn't look *that* wrong ... without knowing if
> the 78 bytes are all it's supposed to be.
>
> 0x6db67b is followed by 0x6db67c, take the 0 bytes from 0x6db67b and add
> the 78 from 0x6db67c and we have something that the card thinks is ok. I
> wonder if it contains something useful.
>
Is there some way to find out?
[...]
> Just a broadcast version of 8d00, I think. Yep, all that needs to be done
> is solve the 8d00's, then the rest will follow ...
>
Well doesn't look too bad, does it :-/
>
> silly suggestions/questions
>
> + which compiler? gcc-2.95.183567-latest-cvs-thingy or some more common
> (egcs-1.1.2 myself), you could try compiling it with an older
> "safer" compiler (failing that, try a newer, more improved one :)
>
No cutting-edge stuff. Just a standard RedHat 6.2 installation with
egcs-1.1.2. I don't want to use gcc-1.95 now, because of the known issues
(esp. with the kernel).
> + do you have the possibility to test 2.4.0-test1-ac12?
> (or whatever the latest may be). The 2.3/2.4 driver does the locking
> (and PCI setup magic) differently, probably doesn't matter but it might
> be worth trying.
>
Sorry I can't. Currently I don't have the resources (machine-wise and
time-wise). I should get some assistance in a month or so, and then I
could have some time.
Bye,
Konrad
========================================================================
Konrad Podloucky <[EMAIL PROTECTED]> Tel:+43-1-810 09 99/11
IP Software Systems http://www.cc8.com Fax:+43-1-810 09 99/9
System Administration
========================================================================
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]