public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Calin Onofrei" <conofrei@plantcml.com>
To: "Andrew Lunn" <andrew@lunn.ch>
Cc: <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Error when changing 'fconfig' redboot values from a linux  program
Date: Wed, 17 May 2006 19:50:00 -0000	[thread overview]
Message-ID: <EEBEE767A519B74FA68C00324A95902305DBEC73@porthos.cml.com> (raw)

Now is working, I can read/write Redboot configuration from a linux
program. Before writing I use the ioctl MEMERASE and erase the whole
RedBoot config block.
Thanks Andrew for your suggestion.

Calin Onofrei. 

-----Original Message-----
From: Andrew Lunn [mailto:andrew@lunn.ch] 
Sent: Wednesday, May 17, 2006 11:03 AM
To: Calin Onofrei
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Error when changing 'fconfig' redboot values from a
linux program

On Wed, May 17, 2006 at 10:51:23AM -0400, Calin Onofrei wrote:
> Thierry,
> 
> In my case RedBoot config is on mtd5 partition (do cat /proc/mtd to
see) and I open the device:
> Open("/dev/mtd5", O_RDWR | O_SYNC). With the handle returned by the
open function I do read and write operations as for any other device.

But is /dev/mtd5 like any other device? Or do you need to erase it using
an ioctl call?

I don't know, but maybe you need to find out.

  Andrew

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2006-05-17 19:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17 19:50 Calin Onofrei [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-17 15:12 Calin Onofrei
2006-05-17 14:51 Calin Onofrei
2006-05-17 15:05 ` Andrew Lunn
2006-05-17 13:34 Calin Onofrei
2006-05-17 14:12 ` thierry langlais

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=EEBEE767A519B74FA68C00324A95902305DBEC73@porthos.cml.com \
    --to=conofrei@plantcml.com \
    --cc=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).