All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Hunter <ext-adrian.hunter@nokia.com>
To: Kyungmin Park <kmpark@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [REFERENCE PATCH][OneNAND] S3C64XX support
Date: Tue, 21 Oct 2008 10:04:02 +0300	[thread overview]
Message-ID: <48FD7EE2.6090906@nokia.com> (raw)
In-Reply-To: <9c9fda240810201601m2f5fbf9bqb5180c3617c01221@mail.gmail.com>

Kyungmin Park wrote:
> On Tue, Oct 21, 2008 at 12:07 AM, Adrian Hunter
> <ext-adrian.hunter@nokia.com> wrote:
>> Kyungmin Park wrote:
>>> It's OneNAND support on New Samsung Mobile CPU S3C64XX series Now it's
>>> only tested with s3c6410 with UBI & UBIFS.
>>> If you want to use it on s3c6400, you should change some values.
>>>
>>> There's some ugly hack for support s3c64xx. It will be handled more fancy
>>> later.
>>>
>>> Any comments are welcome
>> Why not just make it a separate driver and skip using onenand_base etc?
>>
> 
> DId you see the s3c64xx OneNAND controller?. It has its own OneNAND
> controller and don't use the OneNAND memory access method as OMAP.
> 
> Yes it's possible to make an own OneNAND driver for s3c64xx, but maybe
> a half of codes are redundant except the access method  so I want to
> use default onenand_base and just redefine the OneNAND function for
> s3c64xx.


I glanced at the code.  It did not look like there was much code from
onenand_base that was needed, so wouldn't it be cleaner to just copy
those bits?

      reply	other threads:[~2008-10-21  7:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20  9:32 [REFERENCE PATCH][OneNAND] S3C64XX support Kyungmin Park
2008-10-20 15:07 ` Adrian Hunter
2008-10-20 23:01   ` Kyungmin Park
2008-10-21  7:04     ` Adrian Hunter [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=48FD7EE2.6090906@nokia.com \
    --to=ext-adrian.hunter@nokia.com \
    --cc=kmpark@infradead.org \
    --cc=linux-mtd@lists.infradead.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.