Linux MIPS Architecture development
 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 23:32:40 +0100	[thread overview]
Message-ID: <45BBD308.4060207@wp.pl> (raw)
In-Reply-To: <200701272238.08482.florian.fainelli@int-evry.fr>

[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]

<cut>

>There might be version mismatch, or other modules to load before this one. 
>This can also be a kernel configuration problem, related to modules that are 
>expected to be in-kernel.
>
>  
>
You gave me an idea: i think it's related to fact, that those modules
expect to be linked into kernel (they complain about basic kernel
symbols too). But how to make sure?? - not risking to render board unusable?
If you find a method (maybe trying to link a non network-critical module
into kernel, like ipsec), please provide step-by-step instructions to me.


<cut>
>>Well, unless you have erased the booloader, I think you should still
be able
>>to reflash the device using bootloader commands, even via xmodem if
the loader allows it.

You THINK or you KNOW? (in case of 8186!)

>>I think you should have a look at this page [1], where there are
ressources to create custom rtl8181 firmwares.

I will, but on my board there is 8186, not 8181. And very beginning of
bootstrap, in bootloader i can see no option of TFTP (see atached file).

W.P.

[-- Attachment #2: bootloader.txt --]
[-- Type: text/plain, Size: 637 bytes --]


UART1 output test ok
Uart init
mfid=000000c2 devid=00002249
Found 1 x 2M flash memory

---RealTek(RTL8186)at 2005.06.06-11:22+0800 version 1.3c [32bit](180MHz)

---Escape booting by user
<RealTek>help
----------------- COMMAND MODE HELP ------------------
HELP (?)				    : Print this help message
D <Address> <Len>
EW <Address> <Value1> <Value2>...
EH <Address> <Value1> <Value2>...
EB <Address> <Value1> <Value2>...
EC <Address> <Value1> <Length>...
CMP: CMP <dst><src><length>
IPCONFIG:<TargetAddress>
J: Jump to <TargetAddress>
FLW: FLW <dst><src><length>
FLR: FLR <dst><src><length>
LOADADDR: <Load Address>
AUTOBURN: 0/1
<RealTek>

  reply	other threads:[~2007-01-27 22:31 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.
2007-01-27 21:38         ` Florian Fainelli
2007-01-27 22:32           ` W.P. [this message]
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=45BBD308.4060207@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox