From: Wan Zongshun <vw@iommu.org>
To: Arnd Bergmann <arnd@arndb.de>, linux-arm-kernel@lists.infradead.org
Cc: Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Wan ZongShun <mcuos.com@gmail.com>,
linux-kernel@vger.kernel.org,
Mike Thompson <mpthompson@gmail.com>
Subject: Re: [PATCH] mtd: nuc900_nand: read correct SMISR register
Date: Fri, 15 Jan 2016 15:53:41 +0800 [thread overview]
Message-ID: <5698A585.7060007@iommu.org> (raw)
In-Reply-To: <4251392.DUmfQyrPag@wuerfel>
>>
>> Actually, Nuvoton should still leverage this upstream w90x900 codes for
>> their old and new arm chip BSP, but I am not sure their open source plan
>> for the new chip now, I will check with Nuvoton for this topic, and give
>> you feedback here, so please hold on its removal.
>
> Ok, sure. Thanks for the quick reply!
>
> I've had a look around at the current produce lineup, and it seems that
> nuc900 (w90x900) is still marketed, and as you say is similar to the n329
> series.
>
> There has been one attempt to do a modern port for n329 in 2014 but
> it never got submitted. See http://comments.gmane.org/gmane.linux.kernel.kernelnewbies/49077
> and https://github.com/mpthompson/linux/tree/n329
>
> The code looks rather nice, so it's a pity that the effort stalled,
> but it should not be hard for anyone to start out with Mike's tree
> and forward-port it to 4.5.
I will try to get this board you mentioned and try to cowork Mike to
submit it into upstream.
After checking with Nuvoton people, and I will get another board and
help them update the latest kernel BSP and also submit new nuc970 chip
BSP into upstream.
spec:
http://www.nuvoton.com/hq/products/microprocessors/arm9-mpus/nuc900-series/?__locale=en
>
> Arnd
>
WARNING: multiple messages have this Message-ID (diff)
From: vw@iommu.org (Wan Zongshun)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mtd: nuc900_nand: read correct SMISR register
Date: Fri, 15 Jan 2016 15:53:41 +0800 [thread overview]
Message-ID: <5698A585.7060007@iommu.org> (raw)
In-Reply-To: <4251392.DUmfQyrPag@wuerfel>
>>
>> Actually, Nuvoton should still leverage this upstream w90x900 codes for
>> their old and new arm chip BSP, but I am not sure their open source plan
>> for the new chip now, I will check with Nuvoton for this topic, and give
>> you feedback here, so please hold on its removal.
>
> Ok, sure. Thanks for the quick reply!
>
> I've had a look around at the current produce lineup, and it seems that
> nuc900 (w90x900) is still marketed, and as you say is similar to the n329
> series.
>
> There has been one attempt to do a modern port for n329 in 2014 but
> it never got submitted. See http://comments.gmane.org/gmane.linux.kernel.kernelnewbies/49077
> and https://github.com/mpthompson/linux/tree/n329
>
> The code looks rather nice, so it's a pity that the effort stalled,
> but it should not be hard for anyone to start out with Mike's tree
> and forward-port it to 4.5.
I will try to get this board you mentioned and try to cowork Mike to
submit it into upstream.
After checking with Nuvoton people, and I will get another board and
help them update the latest kernel BSP and also submit new nuc970 chip
BSP into upstream.
spec:
http://www.nuvoton.com/hq/products/microprocessors/arm9-mpus/nuc900-series/?__locale=en
>
> Arnd
>
next prev parent reply other threads:[~2016-01-15 7:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 21:38 [PATCH] mtd: nuc900_nand: read correct SMISR register Arnd Bergmann
2016-01-13 21:38 ` Arnd Bergmann
2016-01-13 21:50 ` Brian Norris
2016-01-13 21:50 ` Brian Norris
2016-01-13 22:02 ` Arnd Bergmann
2016-01-13 22:02 ` Arnd Bergmann
2016-01-14 0:29 ` Brian Norris
2016-01-14 0:29 ` Brian Norris
2016-01-14 9:34 ` Wan Zongshun
2016-01-14 9:34 ` Wan Zongshun
2016-01-14 12:08 ` Arnd Bergmann
2016-01-14 12:08 ` Arnd Bergmann
2016-01-15 7:53 ` Wan Zongshun [this message]
2016-01-15 7:53 ` Wan Zongshun
2016-01-15 11:03 ` Arnd Bergmann
2016-01-15 11:03 ` Arnd Bergmann
2016-01-15 15:01 ` Wan Zongshun
2016-01-15 15:01 ` Wan Zongshun
2016-01-15 18:03 ` Brian Norris
2016-01-15 18:03 ` 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=5698A585.7060007@iommu.org \
--to=vw@iommu.org \
--cc=arnd@arndb.de \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mcuos.com@gmail.com \
--cc=mpthompson@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.