From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Rob Landley <rob@landley.net>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Jiri Slaby <jslaby@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Kevin Hilman <khilman@linaro.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Vivek Goyal <vgoyal@redhat.com>,
"Steven Rostedt (Red Hat)" <rostedt@goodmis.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Riku Voipio <riku.voipio@linaro.org>,
Jiri Kosina <jkosina@suse.cz>, Paul Bolle <pebolle@tiscali.nl>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Davidlohr Bueso <davidlohr@hp.com>,
Richard Weinberger <richard@nod.at>, Zhigang Lu <zlu@tilera.com>,
Vineet Gupta <vgupta@synopsys.com>,
Richard Kuo <rkuo@codeaurora.org>,
Max Filippov <jcmvbkbc@gmail.com>,
Pranith Kumar <bobby.prani@gmail.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
linux-kernel@vger.kernel.or
Subject: Re: [PATCH 2/2] Changes to existing files for 0PF FPGA board.
Date: Mon, 22 Jun 2015 04:26:01 +0000 [thread overview]
Message-ID: <87381ktlly.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <5585C952.6020406@landley.net>
On Sun, 21 Jun 2015 05:13:06 +0900,
Rob Landley wrote:
>
> On 06/20/2015 03:00 AM, Geert Uytterhoeven wrote:
> > Hi Rob,
> >
> > On Sat, Jun 20, 2015 at 12:11 AM, Rob Landley <rob@landley.net> wrote:
> >> On 06/18/2015 02:36 PM, Geert Uytterhoeven wrote:
> >>> On Thu, Jun 18, 2015 at 7:19 PM, Rob Landley <rob@landley.net> wrote:
> >>>> Changes to existing files to add 0pf j2 board support.
> >>>
> >>> Thanks for your patch!
> >>>
> >>> Like Greg already said, splitting it up in logical parts and providing useful
> >>> patch descriptions would be highly appreciated.
> >>
> >> I actually don't know how to split it up further. The initial port was
> >> done by a series of contractors (in Russia, I think), and then I
> >> inherited it to try to get something releasable. This is the smallest
> >> chunk I could get to actually boot.
> >>
> >> I suppose I could send you the serial driver by itself, and _then_ the
> >> board, but it wouldn't compile if nothing uses it. (Similarly you can't
> >> boot the board without a serial console...)
> >
> > You don't have to send in a big initial patch that actually boots.
> > For new architecture/SoC/board support, just split it in logical hunks,
> > and submit it in some logical order that always builds.
> >
> > E.g.:
> > - SoC core support (arch/sh/),
> > - Board support (arch/sh/),
> > - Drivers.
> >
> > The first two should go in through akpm (sh is orphaned),
> > the rest through the individual subsystem maintainers.
>
> I'm aware sh is orphaned
> (http://www.openwall.com/lists/musl/2014/02/17/3). I'm trying to do
> something about that.
>
> I'm not up to maintaining an architecture myself (after the
> kernel.org/doc thing I walked away from kernel stuff for most of a year,
> as you can see I'm a bit out of practice), but I spoke to Yoshinori Sato
> (who used to maintain sh2, and only dropped it when renesas discontinued
> the hardware) and he said he might be interested in returning as a
> co-maintainer.
>
> (I note that I've been regression testing and fixing sh4 in my
> aboriginal linux project for several years now, although it's been
> quiescent enough on the kernel side the majority of my posts about it
> seem to be qemu issues, from
> https://lists.gnu.org/archive/html/qemu-devel/2010-03/msg00976.html to
> http://comments.gmane.org/gmane.comp.emulators.qemu/294066 . Dealing
> with sh2 is new to me, but it's also my day job these days. :)
>
> >> (Now the reason _I_ thought you'd reject it had more to do with not
> >> having converted it to device tree yet, and things on that level. But I
> >
> > Sh is an existing supported architecture, so DT is not a hard requirement.
>
> Yeah, but new board... And it's the right thing to do.
I think convert DT is best way.
It looks don't use SH compatible peripherals.
I think if it's a SH compatible, it's better to maintain
the platform_device structure.
But use incompatible peripherals (So need new platform_device),
It's difficult to maintain it.
I trying SE7619 target convert to DT. It works fine.
So no problem in 0PF platform DT support.
> > If you would have waited until after the removal of sh, it would be much
> > harder :-) (cfr. h8300, but Sato-san did a great job there, with DT, CCF, ...)
>
> Indeed he did. We had lunch with him when I was in Japan a couple weeks ago.
>
> I've got the references I need to do this, just... lots of shoveling on
> a lot of fronts to do right now. (And I mentioned like 3 other things I
> already know I need to fix in the 0/2 message.)
>
> >> wanted to get it out there so people outside $DAYJOB can test the
> >> hardware. We did a linuxcon japan presentation which lwn.net covered,
> >> and we're getting pokes about "where can I download this", so...)
> >
> > It's great to hear there's so much interest in this! Let's hope this will
> > attract more actual contributors...
>
> The "where can I download this" is now the developer tab of 0pf.org by
> the way. And the mailing lists are on lists.nommu.org.
>
> I'll try to submit an updated patch set in the next couple days.
>
> Thanks,
>
> Rob
--
Yoshinori Sato
<ysato@users.sourceforge.jp>
--
To unsubscribe from this list: send the line "unsubscribe linux-sh" in
WARNING: multiple messages have this Message-ID (diff)
From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Rob Landley <rob@landley.net>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Jiri Slaby <jslaby@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Kevin Hilman <khilman@linaro.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Vivek Goyal <vgoyal@redhat.com>,
"Steven Rostedt (Red Hat)" <rostedt@goodmis.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Riku Voipio <riku.voipio@linaro.org>,
Jiri Kosina <jkosina@suse.cz>, Paul Bolle <pebolle@tiscali.nl>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Davidlohr Bueso <davidlohr@hp.com>,
Richard Weinberger <richard@nod.at>, Zhigang Lu <zlu@tilera.com>,
Vineet Gupta <vgupta@synopsys.com>,
Richard Kuo <rkuo@codeaurora.org>,
Max Filippov <jcmvbkbc@gmail.com>,
Pranith Kumar <bobby.prani@gmail.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
linux-kernel@vger.kernel.or
Subject: Re: [PATCH 2/2] Changes to existing files for 0PF FPGA board.
Date: Mon, 22 Jun 2015 13:26:01 +0900 [thread overview]
Message-ID: <87381ktlly.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <5585C952.6020406@landley.net>
On Sun, 21 Jun 2015 05:13:06 +0900,
Rob Landley wrote:
>
> On 06/20/2015 03:00 AM, Geert Uytterhoeven wrote:
> > Hi Rob,
> >
> > On Sat, Jun 20, 2015 at 12:11 AM, Rob Landley <rob@landley.net> wrote:
> >> On 06/18/2015 02:36 PM, Geert Uytterhoeven wrote:
> >>> On Thu, Jun 18, 2015 at 7:19 PM, Rob Landley <rob@landley.net> wrote:
> >>>> Changes to existing files to add 0pf j2 board support.
> >>>
> >>> Thanks for your patch!
> >>>
> >>> Like Greg already said, splitting it up in logical parts and providing useful
> >>> patch descriptions would be highly appreciated.
> >>
> >> I actually don't know how to split it up further. The initial port was
> >> done by a series of contractors (in Russia, I think), and then I
> >> inherited it to try to get something releasable. This is the smallest
> >> chunk I could get to actually boot.
> >>
> >> I suppose I could send you the serial driver by itself, and _then_ the
> >> board, but it wouldn't compile if nothing uses it. (Similarly you can't
> >> boot the board without a serial console...)
> >
> > You don't have to send in a big initial patch that actually boots.
> > For new architecture/SoC/board support, just split it in logical hunks,
> > and submit it in some logical order that always builds.
> >
> > E.g.:
> > - SoC core support (arch/sh/),
> > - Board support (arch/sh/),
> > - Drivers.
> >
> > The first two should go in through akpm (sh is orphaned),
> > the rest through the individual subsystem maintainers.
>
> I'm aware sh is orphaned
> (http://www.openwall.com/lists/musl/2014/02/17/3). I'm trying to do
> something about that.
>
> I'm not up to maintaining an architecture myself (after the
> kernel.org/doc thing I walked away from kernel stuff for most of a year,
> as you can see I'm a bit out of practice), but I spoke to Yoshinori Sato
> (who used to maintain sh2, and only dropped it when renesas discontinued
> the hardware) and he said he might be interested in returning as a
> co-maintainer.
>
> (I note that I've been regression testing and fixing sh4 in my
> aboriginal linux project for several years now, although it's been
> quiescent enough on the kernel side the majority of my posts about it
> seem to be qemu issues, from
> https://lists.gnu.org/archive/html/qemu-devel/2010-03/msg00976.html to
> http://comments.gmane.org/gmane.comp.emulators.qemu/294066 . Dealing
> with sh2 is new to me, but it's also my day job these days. :)
>
> >> (Now the reason _I_ thought you'd reject it had more to do with not
> >> having converted it to device tree yet, and things on that level. But I
> >
> > Sh is an existing supported architecture, so DT is not a hard requirement.
>
> Yeah, but new board... And it's the right thing to do.
I think convert DT is best way.
It looks don't use SH compatible peripherals.
I think if it's a SH compatible, it's better to maintain
the platform_device structure.
But use incompatible peripherals (So need new platform_device),
It's difficult to maintain it.
I trying SE7619 target convert to DT. It works fine.
So no problem in 0PF platform DT support.
> > If you would have waited until after the removal of sh, it would be much
> > harder :-) (cfr. h8300, but Sato-san did a great job there, with DT, CCF, ...)
>
> Indeed he did. We had lunch with him when I was in Japan a couple weeks ago.
>
> I've got the references I need to do this, just... lots of shoveling on
> a lot of fronts to do right now. (And I mentioned like 3 other things I
> already know I need to fix in the 0/2 message.)
>
> >> wanted to get it out there so people outside $DAYJOB can test the
> >> hardware. We did a linuxcon japan presentation which lwn.net covered,
> >> and we're getting pokes about "where can I download this", so...)
> >
> > It's great to hear there's so much interest in this! Let's hope this will
> > attract more actual contributors...
>
> The "where can I download this" is now the developer tab of 0pf.org by
> the way. And the mailing lists are on lists.nommu.org.
>
> I'll try to submit an updated patch set in the next couple days.
>
> Thanks,
>
> Rob
--
Yoshinori Sato
<ysato@users.sourceforge.jp>
--
To unsubscribe from this list: send the line "unsubscribe linux-sh" in
WARNING: multiple messages have this Message-ID (diff)
From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Rob Landley <rob@landley.net>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Jiri Slaby <jslaby@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Kevin Hilman <khilman@linaro.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Vivek Goyal <vgoyal@redhat.com>,
"Steven Rostedt (Red Hat)" <rostedt@goodmis.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Riku Voipio <riku.voipio@linaro.org>,
Jiri Kosina <jkosina@suse.cz>, Paul Bolle <pebolle@tiscali.nl>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Davidlohr Bueso <davidlohr@hp.com>,
Richard Weinberger <richard@nod.at>, Zhigang Lu <zlu@tilera.com>,
Vineet Gupta <vgupta@synopsys.com>,
Richard Kuo <rkuo@codeaurora.org>,
Max Filippov <jcmvbkbc@gmail.com>,
Pranith Kumar <bobby.prani@gmail.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>
Subject: Re: [PATCH 2/2] Changes to existing files for 0PF FPGA board.
Date: Mon, 22 Jun 2015 13:26:01 +0900 [thread overview]
Message-ID: <87381ktlly.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <5585C952.6020406@landley.net>
On Sun, 21 Jun 2015 05:13:06 +0900,
Rob Landley wrote:
>
> On 06/20/2015 03:00 AM, Geert Uytterhoeven wrote:
> > Hi Rob,
> >
> > On Sat, Jun 20, 2015 at 12:11 AM, Rob Landley <rob@landley.net> wrote:
> >> On 06/18/2015 02:36 PM, Geert Uytterhoeven wrote:
> >>> On Thu, Jun 18, 2015 at 7:19 PM, Rob Landley <rob@landley.net> wrote:
> >>>> Changes to existing files to add 0pf j2 board support.
> >>>
> >>> Thanks for your patch!
> >>>
> >>> Like Greg already said, splitting it up in logical parts and providing useful
> >>> patch descriptions would be highly appreciated.
> >>
> >> I actually don't know how to split it up further. The initial port was
> >> done by a series of contractors (in Russia, I think), and then I
> >> inherited it to try to get something releasable. This is the smallest
> >> chunk I could get to actually boot.
> >>
> >> I suppose I could send you the serial driver by itself, and _then_ the
> >> board, but it wouldn't compile if nothing uses it. (Similarly you can't
> >> boot the board without a serial console...)
> >
> > You don't have to send in a big initial patch that actually boots.
> > For new architecture/SoC/board support, just split it in logical hunks,
> > and submit it in some logical order that always builds.
> >
> > E.g.:
> > - SoC core support (arch/sh/),
> > - Board support (arch/sh/),
> > - Drivers.
> >
> > The first two should go in through akpm (sh is orphaned),
> > the rest through the individual subsystem maintainers.
>
> I'm aware sh is orphaned
> (http://www.openwall.com/lists/musl/2014/02/17/3). I'm trying to do
> something about that.
>
> I'm not up to maintaining an architecture myself (after the
> kernel.org/doc thing I walked away from kernel stuff for most of a year,
> as you can see I'm a bit out of practice), but I spoke to Yoshinori Sato
> (who used to maintain sh2, and only dropped it when renesas discontinued
> the hardware) and he said he might be interested in returning as a
> co-maintainer.
>
> (I note that I've been regression testing and fixing sh4 in my
> aboriginal linux project for several years now, although it's been
> quiescent enough on the kernel side the majority of my posts about it
> seem to be qemu issues, from
> https://lists.gnu.org/archive/html/qemu-devel/2010-03/msg00976.html to
> http://comments.gmane.org/gmane.comp.emulators.qemu/294066 . Dealing
> with sh2 is new to me, but it's also my day job these days. :)
>
> >> (Now the reason _I_ thought you'd reject it had more to do with not
> >> having converted it to device tree yet, and things on that level. But I
> >
> > Sh is an existing supported architecture, so DT is not a hard requirement.
>
> Yeah, but new board... And it's the right thing to do.
I think convert DT is best way.
It looks don't use SH compatible peripherals.
I think if it's a SH compatible, it's better to maintain
the platform_device structure.
But use incompatible peripherals (So need new platform_device),
It's difficult to maintain it.
I trying SE7619 target convert to DT. It works fine.
So no problem in 0PF platform DT support.
> > If you would have waited until after the removal of sh, it would be much
> > harder :-) (cfr. h8300, but Sato-san did a great job there, with DT, CCF, ...)
>
> Indeed he did. We had lunch with him when I was in Japan a couple weeks ago.
>
> I've got the references I need to do this, just... lots of shoveling on
> a lot of fronts to do right now. (And I mentioned like 3 other things I
> already know I need to fix in the 0/2 message.)
>
> >> wanted to get it out there so people outside $DAYJOB can test the
> >> hardware. We did a linuxcon japan presentation which lwn.net covered,
> >> and we're getting pokes about "where can I download this", so...)
> >
> > It's great to hear there's so much interest in this! Let's hope this will
> > attract more actual contributors...
>
> The "where can I download this" is now the developer tab of 0pf.org by
> the way. And the mailing lists are on lists.nommu.org.
>
> I'll try to submit an updated patch set in the next couple days.
>
> Thanks,
>
> Rob
--
Yoshinori Sato
<ysato@users.sourceforge.jp>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2015-06-22 4:26 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 17:19 [PATCH 0/2] 0pf-j2 (sh2-compatible open hardware) FPGA board support Rob Landley
2015-06-18 17:19 ` Rob Landley
2015-06-18 17:19 ` [PATCH 1/2] New files for 0PF FPGA board Rob Landley
2015-06-18 17:19 ` Rob Landley
2015-06-19 7:47 ` Geert Uytterhoeven
2015-06-19 7:47 ` Geert Uytterhoeven
2015-06-18 17:19 ` [PATCH 2/2] Changes to existing " Rob Landley
2015-06-18 17:19 ` Rob Landley
2015-06-18 17:19 ` Rob Landley
2015-06-18 17:59 ` Greg Kroah-Hartman
2015-06-18 17:59 ` Greg Kroah-Hartman
2015-06-18 19:02 ` Steven Rostedt
2015-06-18 19:02 ` Steven Rostedt
2015-06-19 21:57 ` Rob Landley
2015-06-19 21:57 ` Rob Landley
2015-06-19 21:57 ` Rob Landley
2015-06-19 22:49 ` Greg Kroah-Hartman
2015-06-19 22:49 ` Greg Kroah-Hartman
2015-06-27 3:21 ` Rob Landley
2015-06-18 19:36 ` Geert Uytterhoeven
2015-06-18 19:36 ` Geert Uytterhoeven
2015-06-18 19:36 ` Geert Uytterhoeven
2015-06-19 22:11 ` Rob Landley
2015-06-19 22:11 ` Rob Landley
2015-06-19 22:11 ` Rob Landley
2015-06-20 8:00 ` Geert Uytterhoeven
2015-06-20 8:00 ` Geert Uytterhoeven
2015-06-20 8:00 ` Geert Uytterhoeven
2015-06-20 20:13 ` Rob Landley
2015-06-20 20:13 ` Rob Landley
2015-06-20 20:13 ` Rob Landley
2015-06-20 20:48 ` Geert Uytterhoeven
2015-06-20 20:48 ` Geert Uytterhoeven
2015-06-20 20:48 ` Geert Uytterhoeven
2015-06-22 4:26 ` Yoshinori Sato [this message]
2015-06-22 4:26 ` Yoshinori Sato
2015-06-22 4:26 ` Yoshinori Sato
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=87381ktlly.wl-ysato@users.sourceforge.jp \
--to=ysato@users.sourceforge.jp \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=davidlohr@hp.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=jcmvbkbc@gmail.com \
--cc=jkosina@suse.cz \
--cc=jslaby@suse.cz \
--cc=khilman@linaro.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.or \
--cc=linux-sh@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pebolle@tiscali.nl \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=richard@nod.at \
--cc=riku.voipio@linaro.org \
--cc=rkuo@codeaurora.org \
--cc=rob@landley.net \
--cc=rostedt@goodmis.org \
--cc=vgoyal@redhat.com \
--cc=vgupta@synopsys.com \
--cc=zlu@tilera.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.