All of lore.kernel.org
 help / color / mirror / Atom feed
From: "W.P." <laurentp@wp.pl>
To: Florian Fainelli <florian.fainelli@int-evry.fr>,
	linux-mips@linux-mips.org
Subject: Re: RTL-8186 follow-up
Date: Sat, 27 Jan 2007 18:31:09 +0100	[thread overview]
Message-ID: <45BB8C5D.50405@wp.pl> (raw)
In-Reply-To: <200701271354.41905.florian.fainelli@int-evry.fr>

<cut>
1). I have added modules found in KERNEL_SRC/rtl8186 (that i wrote about
in other post), to image, but trying to load them gives "unresolved
symbol" errors:

<example>
# insmod ip_nat_l2tp
Using /lib/modules/2.4.18-MIPS-01.00/ip_nat_l2tp.o
insmod: unresolved symbol kmalloc
insmod: unresolved symbol create_proc_entry
insmod: unresolved symbol ip_nat_helper_register
insmod: unresolved symbol ip_nat_helper_unregister
insmod: unresolved symbol csum_partial
insmod: unresolved symbol sprintf
</example>

This problem is very of interest, because there are modules for IP_SEC,
and a module rtl8186 (NIC driver??) that is much SMALLER that module
with the same name rtl8186 generated during kernel compilation. There is
also module named wireless_ag_net.

2). Is there some possibility to "recover" using serial port if it
happens to corrupt kernel to point to not have network access? (I mean
NOT using JTAG).??

3). Florian, could you help me to "reverse engineer" Edimax-supplied
firmware image? AFAIR it is composed of header, compressed vmlinux and
compressed initrd. But how to find at what offset those images are?, and
how are they compressed.

W.P.

  parent reply	other threads:[~2007-01-27 17:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-26 21:36 Beginning with REALTEK RTL-8186 Don Hiatt
2007-01-26 23:55 ` W.P.
2007-01-27 13:04   ` RTL-8186 follow-up W.P.
     [not found]     ` <200701271354.41905.florian.fainelli@int-evry.fr>
2007-01-27 15:46       ` W.P.
2007-01-27 17:31       ` W.P. [this message]
2007-01-27 21:38         ` Florian Fainelli
2007-01-27 22:32           ` W.P.
2007-01-29 19:54       ` RTL-8186 follow-up2 W.P.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45BB8C5D.50405@wp.pl \
    --to=laurentp@wp.pl \
    --cc=florian.fainelli@int-evry.fr \
    --cc=linux-mips@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.