Hi Jiri,

Thanks for testing. :) I've added your VID:PID pair to the driver and also
corrected some printf calls and variable types so now it's possible to
compile driver cleanly on IA-32.

Regards.
Agnieszka


On Fri, Jul 4, 2014 at 2:09 PM, Jiri Svoboda <[email protected]>
wrote:

> Hi Agniezka et al,
>
> I tried the rtl8169 driver on my workstation Kvadrat. The first thing I
> encountered was a problem with compilation - I tried compiling for ia32,
> but that failed. I've yet to compile a 64-bit compiler. So I fixed/worked
> around the compilation issues and booted the system.
>
> The driver did not attach - I found out that my Realtek is a RTL8168, PCI
> VID:PID is 10EC:8168. I added those to the .ma file and booted again. The
> drivrer attached and correctly read out the MAC address. I connected via a
> cable to my laptop and ran Wireshark on the other side. Configured an IP
> address and tried pinging.
>
> The result: frames were properly being sent (Wireshark saw them), but the
> responses were apparently not being received. Unfortunately I did not have
> the time to dig deeper into it.
>
> Would you expect this kind of behavior if the driver did not receive any
> interrupts at all? Or would it not work at all?
>
> Given that USB is not working on that machine and I am sometimes getting
> 'spurious interrupt' messages for keypresses (currently only if the system
> does not boot all the way to the desktop), it could be a problem with
> interrupt handling on my machine, rather than with the driver.
>
> Best regards,
> Jiri
>
>
> _______________________________________________
> HelenOS-devel mailing list
> [email protected]
> http://lists.modry.cz/listinfo/helenos-devel
>
>
_______________________________________________
HelenOS-devel mailing list
[email protected]
http://lists.modry.cz/listinfo/helenos-devel

Reply via email to