From: David Daney <ddaney@avtrex.com>
To: "W.P." <laurentp@wp.pl>
Cc: linux-mips@linux-mips.org
Subject: Re: Advice needed.
Date: Wed, 31 Jan 2007 09:22:40 -0800 [thread overview]
Message-ID: <45C0D060.1070903@avtrex.com> (raw)
In-Reply-To: <45C0C956.2050009@wp.pl>
W.P. wrote:
> Hello,
> currently i am "fighting" with Edimax BR-6024Wg, (Realtek-8186 based,
> lexra-mips). I need an advice from a system developer/programmer:
>
> 1). When using original firmware (EDIMAX-developed Linux-mips), task of
> upgrading firmware is done by web server binary: webs, which is GoAhead
> 2.1.1, BUT Edimax didn't published "applets" -> C functions, that
> implement real functionality.
>
> 2). In /dev directory there is a block node with mtd name. I have cat'ed
> it's contents to /web, and downloaded to PC. File seems to be raw
> contents of Flash memory: 2048*1024bytes long. If I drop first 64kB and
> truncate file to same length that Edimax-supplied firmware, files show
> to be the same (using cmp). The first 64kB looks to contain among
> others, variables used in BR system. There is originally an utility
> "flash" to get/set variables.
>
> Now the question:
> When I will have a new firmware (image) will it be safe(!?) to do such
> thing: (instead of using webs binary):
> cat /dev/mtd > some.file
> dd first 64k of some.file to other.file,
> then download image (from PC) to a third.file
> cat other.file third.file > /dev/mtd back.??????
Using cat or dd to write to /dev/mtd? probably will not work. If there
is a /dev/mtdblock? perhaps. Otherwise use the mtd utilities (flashcp
or nandwrite depending on the type of flash memory) to write to /dev/mtd?.
Take a look at this site for more information:
http://www.linux-mtd.infradead.org/
David Daney
next prev parent reply other threads:[~2007-01-31 17:23 UTC|newest]
Thread overview: 23+ 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 [this message]
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.
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.
-- strict thread matches above, loose matches on Subject: below --
2007-05-25 15:23 zImage.elf loads but does not start Mirek23
2007-05-25 16:56 ` Advice needed Charles Krinke
2006-01-18 17:10 advice needed Babarovic Ivica
2006-01-18 17:19 ` Bill Unruh
2006-01-18 17:35 ` James Carlson
2006-01-19 11:36 ` Babarovic Ivica
2006-01-19 11:41 ` Babarovic Ivica
2006-01-19 17:45 ` Bill Unruh
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=45C0D060.1070903@avtrex.com \
--to=ddaney@avtrex.com \
--cc=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 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.