All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Albrecht Dreß" <albrecht.dress@arcor.de>
To: linuxppc-dev@ozlabs.org
Subject: Re: Q: MTD RAM in OF Device Tree
Date: Tue, 19 May 2009 20:00:36 +0200	[thread overview]
Message-ID: <1242756044.3502.0@antares> (raw)
In-Reply-To: <20090519122714.GH30753@pengutronix.de> (from w.sang@pengutronix.de on Tue May 19 14:27:14 2009)

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

Hi Wolfram!

Am 19.05.09 14:27 schrieb(en) Wolfram Sang:
> I wrote such a driver (yet without partitioning support) and I am  
> trying to get it mainline, just didn't get any comments so far:
> 
> http://patchwork.ozlabs.org/patch/23557/
> http://patchwork.ozlabs.org/patch/23556/

Thanks a lot, this is *exactly* what I was looking for!  Actually,  
partition support is not important as I want to use the whole chip -  
512k isn't *that* much...

> I'd be happy if you could give it a try and donate some  
> {Acked|Tested|Reviewed}-by tags. Maybe this will help for my next try  
> to get it mainline.

Will do that once I get it running completely.  The first test  
triggered some strange problems when I wrote to /dev/mtdn and read back  
the data (which is supposed to give "raw" direct access, right?) - the  
last dword in each 512 byte block is partly broken.  Probably something  
in the localbus layout or timing...

Thanks again,
Albrecht.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2009-05-19 18:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19 11:59 Q: MTD RAM in OF Device Tree Albrecht Dreß
2009-05-19 12:27 ` Wolfram Sang
2009-05-19 14:39   ` Grant Likely
2009-05-19 14:39     ` Grant Likely
2009-05-19 18:00   ` Albrecht Dreß [this message]

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=1242756044.3502.0@antares \
    --to=albrecht.dress@arcor.de \
    --cc=linuxppc-dev@ozlabs.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.