public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Benny Chen <bennyc@rtunet.com>
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Redboot JFFS2 Support
Date: Thu, 28 Jul 2005 05:59:00 -0000	[thread overview]
Message-ID: <1122530343.31422.8159.camel@Vigor4> (raw)
In-Reply-To: <20050713164717.GN29363@lunn.ch>

Hi there,
Cirrus has not get back to me on my intention of releasing their patch
on this list. Hence, I have ported their patch over to work on the
latest ECOS tree from cvs.  I have tested this out on my target and it
seems to work fine.  

Back to my initial problem of getting JFFS2 support for Redboot.  
I have managed to mount the jffs2 directory and read my config file in
RedBoot. But everytime after my application has updated the
configuration file (after the system has booted up) and redboot do a
read on the same file.  I get the below error.

What I saw on the list was that this issue has been fixed. I am using
the latest Redboot from cvs.  Could anyone help?


Thank you very much.

Regards,
Benny 

#----------------------
RedBoot> rtunet_config
rtunet_config:Starting...
rtunet_config:In Verbose Mode
Mount Successful
chdir Successful
Read Open successful
<4>JFFS2 compression type 0x06 not available.
<4>Error: jffs2_decompress returned -5
Read failed -1
Refuse to unmount.
Ino #1 has use count 2
Ino #6 has use count 1
umount failed -1
#----------------------



#----------------------
RedBoot> version
                                                                                
RedBoot(tm) bootstrap and debug environment [ROMRAM]
Non-certified release, version UNKNOWN - built 15:18:04, Jul 28 2005
                                                                                
Platform: Cirrus Logic EDB9301 Board (ARM920T) Rev A
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.
                                                                                
RAM: 0x00000000-0x02000000, [0x00057ce0-0x01fdd000] available
FLASH: 0x60000000 - 0x61000000, 128 blocks of 0x00020000 bytes each.
#----------------------
 





On Thu, 2005-07-14 at 02:47, Andrew Lunn wrote:
> > I just looked at their site, and believe that they've now hidden the 
> > patches behind a registration/login for their eval boards. I was working 
> > with a 3rd party board and don't have access. What to do?
> 
> Before we could get it into CVS Cirrus would have to sign the usual
> copyright assignment. I wanted to know what licensing restrictions
> that had and if there was a contact point.
> 
>         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

  parent reply	other threads:[~2005-07-28  5:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12  4:02 Benny Chen
2005-07-12  6:56 ` Andrew Lunn
2005-07-12 23:47   ` Benny Chen
2005-07-13  6:45     ` Andrew Lunn
2005-07-13 15:55       ` Frank Pagliughi
2005-07-13 16:47         ` Andrew Lunn
2005-07-13 23:43           ` Benny Chen
2005-07-28  5:59           ` Benny Chen [this message]
2005-07-28  7:06             ` Andrew Lunn
2005-07-29  5:24               ` Benny Chen
2005-07-13 23:49         ` Benny Chen
2005-07-31 22:27   ` Benny Chen
2005-08-01  9:47     ` Andrew Lunn

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=1122530343.31422.8159.camel@Vigor4 \
    --to=bennyc@rtunet.com \
    --cc=ecos-discuss@sources.redhat.com \
    /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).