From: "W.P." <laurentp@wp.pl>
To: linux-mips@linux-mips.org
Subject: Re: Advice needed.
Date: Wed, 31 Jan 2007 23:28:34 +0100 [thread overview]
Message-ID: <45C11812.9050808@wp.pl> (raw)
In-Reply-To: <200701312302.05473.florian.fainelli@int-evry.fr>
<cut>
>The board he is talking about is based on a rtl8186 which has few things in
>common with admtek 5120?
>
>
As i realize, it is a MIPS too, and he's talking about utilities, not
the kernel. (I'll download sources tomorrow, i have only GPRS internet
connection, so i will take several hours, and the i'll examine it). At
least some idea ;)
<cut>
>I think you had better using dd rather than cat, because /dev/mtdblock are
>block devices, and should be treated like that. If your image has a valid
>format, i.e : the bootloader accepts it, unless you made important
>modifications to the system code, it should at least be booting.
>
>
Using dd also suggests padding resulting file to 2048*1024 bytes, am i
right? And using block size of 64k?
As of image, i remarked, that file resulting from reading /dev/mtd look
like: boot&variables(64k) + original image I have uploaded using Edimax
program(approx 1.9M) + zeros to the end of 2M boundary.
So you think it may work? (dd ?) Image generation and upload using
Edimax-supplied tools works.
W.P.
next prev parent reply other threads:[~2007-01-31 22:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 16:52 Advice needed W.P.
2007-01-31 17:22 ` David Daney
2007-01-31 18:16 ` W.P.
[not found] ` <1170276219.6791.18.camel@localhost>
2007-01-31 21:34 ` W.P.
2007-01-31 21:39 ` Sergio Aguayo
2007-01-31 21:59 ` Florian Fainelli
2007-01-31 22:28 ` W.P. [this message]
2007-02-01 13:09 ` Sergio Aguayo
2007-02-01 14:50 ` W.P.
2007-02-02 13:43 ` Sergio Aguayo
[not found] ` <45C3BB23.2070309@wp.pl>
2007-02-03 5:57 ` Sergio Aguayo
[not found] ` <45C45DDA.1000805@wp.pl>
2007-02-05 14:34 ` Sergio Aguayo
2007-02-07 18:07 ` W.P.
2007-02-08 15:09 ` Sergio Aguayo
2007-02-08 15:16 ` Sergio Aguayo
2007-02-08 17:41 ` 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=45C11812.9050808@wp.pl \
--to=laurentp@wp.pl \
--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