From: Hauke Mehrtens <hauke@hauke-m.de>
To: "Rafał Miłecki" <zajec5@gmail.com>, linux-mtd@lists.infradead.org
Subject: Re: [RFC 0/3] mtd: bcm47xxnflash: adding support for new NANDs
Date: Sun, 23 Feb 2014 12:31:00 +0100 [thread overview]
Message-ID: <5309DBF4.50305@hauke-m.de> (raw)
In-Reply-To: <1393154819-7369-1-git-send-email-zajec5@gmail.com>
On 02/23/2014 12:26 PM, Rafał Miłecki wrote:
> New Broadcom SoCs have NAND flashes attached & programmed in a totally different
> way. Instead of accessing them with help of ChipCommon core, they can be used
> directly.
>
> To support them we can extend bcm47xxnflash in the way this patches implements.
> However almost nothing in the code will be shared between support for old and
> new devices.
>
> How should we proceed? Implement it that way anyway? Or maybe writing a
> separated driver (bcm53xxnflash?) would be a better idea?
>
Hi,
if this controller is completely different I would suggest writing a new
driver for that controller. Extending the existing driver would make if
just more complex.
Hauke
next prev parent reply other threads:[~2014-02-23 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 11:26 [RFC 0/3] mtd: bcm47xxnflash: adding support for new NANDs Rafał Miłecki
2014-02-23 11:26 ` [RFC 1/3] Revert "mtd: bcm47xxnflash: Use module_platform_driver" Rafał Miłecki
2014-02-23 11:26 ` [RFC 2/3] mtd: bcm47xxnflash: add separated config for platform driver Rafał Miłecki
2014-02-23 11:26 ` [RFC 3/3] mtd: bcm47xxnflash: prepare for adding BCMA driver Rafał Miłecki
2014-02-23 11:31 ` Hauke Mehrtens [this message]
2014-02-26 3:09 ` [RFC 0/3] mtd: bcm47xxnflash: adding support for new NANDs Brian Norris
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=5309DBF4.50305@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=linux-mtd@lists.infradead.org \
--cc=zajec5@gmail.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 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.