public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: tglx@linutronix.de, David Woodhouse <dwmw2@infradead.org>
Cc: Steven Newbury <s_j_newbury@yahoo.co.uk>, linux-mtd@lists.infradead.org
Subject: Re: Fwd: sharpsl nand driver still broken in current git
Date: Sat, 15 Jul 2006 13:01:34 +0100	[thread overview]
Message-ID: <1152964894.5546.77.camel@localhost.localdomain> (raw)
In-Reply-To: <1152269513.24611.183.camel@localhost.localdomain>

On Fri, 2006-07-07 at 12:51 +0200, Thomas Gleixner wrote:
> On Thu, 2006-07-06 at 01:09 +0100, Steven Newbury wrote:
> > > Since the NAND subsystem has been updated from the recent ARM merge the
> > > sharpsl
> > > driver no longer detects the NAND device from nand_scan.
> > > ...
> > > Sharp SL series flash device: 800000 at 0
> > > Using static partision definition
> > > Creating 1 MTD partitions on "sharpsl-flash":
> > > 0x00140000-0x007f0000 : "Boot PROM Filesystem"
> > > No NAND device found!!!
> > > ...
> 
> I converted the driver blindly after I changed the core code. Richard
> can you please look into that ?

The conversion was at fault and a patch to fix it will follow this mail.

I'm loathed to create an mtd git tree containing it as last time I spent
time doing this, the pull request was totally ignored and someone else
ended up duplicating the work.

Richard

      reply	other threads:[~2006-07-15 12:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06  0:09 Fwd: sharpsl nand driver still broken in current git Steven Newbury
2006-07-07 10:51 ` Thomas Gleixner
2006-07-15 12:01   ` Richard Purdie [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=1152964894.5546.77.camel@localhost.localdomain \
    --to=rpurdie@rpsys.net \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=s_j_newbury@yahoo.co.uk \
    --cc=tglx@linutronix.de \
    /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