[OpenRISC] [PATCH 0/7] openrisc: Misc fixes from backlog

[OpenRISC] [PATCH 0/7] openrisc: Misc fixes from backlog

[Stafford Horne]

Forgot to CC the new openrisc list.

On Fri, 16 Sep 2016, Stafford Horne wrote:

> Hello,
>
> This patch is a small set of fixes from the openrisc backlog. These
> changes fix several issues with the openrisc build on modern tool chains
> and address other issues which have cropped up as the kernel as it is
> being used on newer hardware.
>
> Please consider for merge.
>
> On-the-other-hand
>
> The openrisc project has been missing a kernel maintainer
> for some time now. Currently listed in MAINTAINERS is Jonas
> and a website that no longer exists.
>
>
> Some mail threads from Jonas
> https://lkml.org/lkml/2015/5/13/469 - mail from Jonas mentioning
>                                      he is no longer able to maintain
> https://lkml.org/lkml/2015/6/11/426 - mail from Jonas mentioning stefan
>                                      is to be the new maintainer
>
> Ideally stefan kristiansson would become the maintainer but he
> does not have a PGP key signed by kernel maintainers.  Also, he
> does not seem to have much time recently.
>
> We would like some help on how to proceed, options:
> - Someone take these patches into a branch that will be pulled
>   by linus? I can work to maintain the patch queue for openrisc.
> - I can work to get a my PGP key signed and send git pull requests
>   to linus?
>
> Regards,
>  Stafford
>
>
> Christian Svensson (1):
>  openrisc: Add thread-local storage (TLS) support
>
> Guenter Roeck (1):
>  openrisc: Support both old (or32) and new (or1k) toolchain
>
> Jonas Bonn (2):
>  Apply transparent_union attribute to union semun
>  openrisc: restore call-saved regs on sigreturn
>
> Rob Herring (1):
>  openrisc: remove the redundant of_platform_populate
>
> Stefan Kristiansson (2):
>  openrisc: fix PTRS_PER_PGD define
>  openrisc: add SMP and NR_CPUS Kconfig options
>
> arch/openrisc/Kconfig               | 14 ++++++++++++++
> arch/openrisc/include/asm/pgtable.h |  2 +-
> arch/openrisc/kernel/entry.S        | 10 +++++++++-
> arch/openrisc/kernel/process.c      | 13 +++++++++++++
> arch/openrisc/kernel/setup.c        | 10 ----------
> arch/openrisc/kernel/vmlinux.lds.S  |  8 +++++++-
> arch/openrisc/mm/init.c             |  2 +-
> include/uapi/linux/sem.h            |  2 +-
> 8 files changed, 46 insertions(+), 15 deletions(-)
>
> -- 
> 2.7.4
>
>

[OpenRISC] [PATCH 5/7] openrisc: Support both old (or32) and new (or1k) toolchain

[Stafford Horne]

On Mon, 19 Sep 2016, Guenter Roeck wrote:

> On 09/18/2016 11:02 PM, Stafford Horne wrote:
>> 
>>
>>  On Sun, 18 Sep 2016, Guenter Roeck wrote:
>> 
>> >  Tested-by: Guenter Roeck <linux@roeck-us.net>
>> > 
>> >  If you plan to handle openrisc going forward, it would be great if you 
>> >  could
>> >  consider updating MAINTAINERS. The web site and git repository have been 
>> >  unreachable
>> >  for a long time.
>>
>>  Thank you,
>>  Updating maintainers was kind of on my plans, but I figured I need to
>>  prove that I kind of know what I am doing.
>> 
>
> The alternative would be to mark it as Orphaned. Which, for all practical 
> purpose,
> would be the correct state right now.

+CC The openrisc list

Understood, 
I don't think we would want that to happen.

[OpenRISC] [PATCH 5/7] openrisc: Support both old (or32) and new (or1k) toolchain

[Guenter Roeck]

On 09/19/2016 02:11 AM, Stafford Horne wrote:
>
>
> On Mon, 19 Sep 2016, Guenter Roeck wrote:
>
>> On 09/18/2016 11:02 PM, Stafford Horne wrote:
>>>
>>>
>>>  On Sun, 18 Sep 2016, Guenter Roeck wrote:
>>>
>>> >  Tested-by: Guenter Roeck <linux@roeck-us.net>
>>> > >  If you plan to handle openrisc going forward, it would be great if you >  could
>>> >  consider updating MAINTAINERS. The web site and git repository have been >  unreachable
>>> >  for a long time.
>>>
>>>  Thank you,
>>>  Updating maintainers was kind of on my plans, but I figured I need to
>>>  prove that I kind of know what I am doing.
>>>
>>
>> The alternative would be to mark it as Orphaned. Which, for all practical purpose,
>> would be the correct state right now.
>
> +CC The openrisc list
>
> Understood, I don't think we would want that to happen.
>
Look at the entry today:

OPENRISC ARCHITECTURE
M:      Jonas Bonn <jonas@southpole.se>
W:      http://openrisc.net
S:      Maintained
T:      git git://openrisc.net/~jonas/linux
F:      arch/openrisc/

At the very least, W: and T: are incorrect and need to be updated or removed.
Plus, apparently there is a L:, and "T: https://github.com/openrisc/linux"
might be appropriate.

Guenter

[OpenRISC] [PATCH 5/7] openrisc: Support both old (or32) and new (or1k) toolchain

[Stafford Horne]

On Mon, 19 Sep 2016, Guenter Roeck wrote:

> On 09/19/2016 02:11 AM, Stafford Horne wrote:
>> 
>>
>>  On Mon, 19 Sep 2016, Guenter Roeck wrote:
>> 
>> >  On 09/18/2016 11:02 PM, Stafford Horne wrote:
>> > > 
>> > > 
>> > >   On Sun, 18 Sep 2016, Guenter Roeck wrote:
>> > > 
>> > > >   Tested-by: Guenter Roeck <linux@roeck-us.net>
>> > > > >   If you plan to handle openrisc going forward, it would be great 
>> > > > >   if you >  could
>> > > >   consider updating MAINTAINERS. The web site and git repository have 
>> > > >   been >  unreachable
>> > > >   for a long time.
>> > > 
>> > >   Thank you,
>> > >   Updating maintainers was kind of on my plans, but I figured I need to
>> > >   prove that I kind of know what I am doing.
>> > > 
>> > 
>> >  The alternative would be to mark it as Orphaned. Which, for all 
>> >  practical purpose,
>> >  would be the correct state right now.
>>
>>  +CC The openrisc list
>>
>>  Understood, I don't think we would want that to happen.
>> 
> Look at the entry today:
>
> OPENRISC ARCHITECTURE
> M:      Jonas Bonn <jonas@southpole.se>
> W:      http://openrisc.net
> S:      Maintained
> T:      git git://openrisc.net/~jonas/linux
> F:      arch/openrisc/
>
> At the very least, W: and T: are incorrect and need to be updated or removed.
> Plus, apparently there is a L:, and "T: https://github.com/openrisc/linux"
> might be appropriate.
>

Thanks,
I am aware of this, we have since setup a new website, mailing list and as 
you have found, git repo. Stefan has been nominated as the maintainer by 
Jonas on a previous mail thread.

The issue (as we see it) is that neither Stefan or I have signed PGP keys 
by anyone in the web of trust.

I sent this patch set with a cover lett trying to explain of the 
situation trying to get some help.  Your reponses are very helpful.

Do you think I should just send "git pull" reuqests to Linus with a self 
signed pgp key and eplaination to see how it goes?

-Stafford

FYI
I have a change as following in my backlog, as follows:

---
@@ -8691,10 +8063,12 @@ F:      drivers/of/overlay.c
  F:     drivers/of/resolver.c

  OPENRISC ARCHITECTURE
-M:	Jonas Bonn <jonas@southpole.se>
-W:	http://openrisc.net
+M:	Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
+M:	Stafford Horne <shorne@gmail.com>
+W:	http://openrisc.io
+L:	openrisc at lists.librecores.org
+T:	https://github.com/openrisc/linux.git
  S:	Maintained
-T:	git git://openrisc.net/~jonas/linux
  F:	arch/openrisc/

  OPENVSWITCH

--

[OpenRISC] [PATCH 5/7] openrisc: Support both old (or32) and new (or1k) toolchain

[Jonas Bonn]

On 09/19/2016 04:04 PM, Stafford Horne wrote:
>
>
> On Mon, 19 Sep 2016, Guenter Roeck wrote:
>
>> On 09/19/2016 02:11 AM, Stafford Horne wrote:
>>>
>>>
>>>  On Mon, 19 Sep 2016, Guenter Roeck wrote:
>>>
>>> >  On 09/18/2016 11:02 PM, Stafford Horne wrote:
>>> > > > > > >   On Sun, 18 Sep 2016, Guenter Roeck wrote:
>>> > > > > >   Tested-by: Guenter Roeck <linux@roeck-us.net>
>>> > > > >   If you plan to handle openrisc going forward, it would be 
>>> great > > > >   if you > could
>>> > > >   consider updating MAINTAINERS. The web site and git 
>>> repository have > > >   been > unreachable
>>> > > >   for a long time.
>>> > > > >   Thank you,
>>> > >   Updating maintainers was kind of on my plans, but I figured I 
>>> need to
>>> > >   prove that I kind of know what I am doing.
>>> > > > >  The alternative would be to mark it as Orphaned. Which, for 
>>> all >  practical purpose,
>>> >  would be the correct state right now.
>>>
>>>  +CC The openrisc list
>>>
>>>  Understood, I don't think we would want that to happen.
>>>
>> Look at the entry today:
>>
>> OPENRISC ARCHITECTURE
>> M:      Jonas Bonn <jonas@southpole.se>
>> W:      http://openrisc.net
>> S:      Maintained
>> T:      git git://openrisc.net/~jonas/linux
>> F:      arch/openrisc/
>>
>> At the very least, W: and T: are incorrect and need to be updated or 
>> removed.
>> Plus, apparently there is a L:, and "T: 
>> https://github.com/openrisc/linux"
>> might be appropriate.
>>
>
> Thanks,
> I am aware of this, we have since setup a new website, mailing list 
> and as you have found, git repo. Stefan has been nominated as the 
> maintainer by Jonas on a previous mail thread.
>
> The issue (as we see it) is that neither Stefan or I have signed PGP 
> keys by anyone in the web of trust.
>
> I sent this patch set with a cover lett trying to explain of the 
> situation trying to get some help.  Your reponses are very helpful.
>
> Do you think I should just send "git pull" reuqests to Linus with a 
> self signed pgp key and eplaination to see how it goes?

The bigger question I would have at this point is the value of the code 
remaining upstream...  Five years ago, there was a promise to try to get 
the toolchain upstream within a year or two; to this day, I don't know 
that much progress has been made there so this architecture still 
requires a hodge-podge of tools from various sources to build.

Given the toolchain maintainer's general reluctance to move things 
upstream, I'd almost be inclined to just remove the OpenRISC arch from 
the kernel altogether.  Are there any other arch's that can't be built 
with an upstream GCC at this point?

/Jonas

>
> -Stafford
>
> FYI
> I have a change as following in my backlog, as follows:
>
> ---
> @@ -8691,10 +8063,12 @@ F:      drivers/of/overlay.c
>  F:     drivers/of/resolver.c
>
>  OPENRISC ARCHITECTURE
> -M:    Jonas Bonn <jonas@southpole.se>
> -W:    http://openrisc.net
> +M:    Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
> +M:    Stafford Horne <shorne@gmail.com>
> +W:    http://openrisc.io
> +L:    openrisc at lists.librecores.org
> +T:    https://github.com/openrisc/linux.git
>  S:    Maintained
> -T:    git git://openrisc.net/~jonas/linux
>  F:    arch/openrisc/
>
>  OPENVSWITCH
>
> -- 

[OpenRISC] [PATCH 5/7] openrisc: Support both old (or32) and new (or1k) toolchain

[Guenter Roeck]

On 09/19/2016 07:04 AM, Stafford Horne wrote:
>
>
> On Mon, 19 Sep 2016, Guenter Roeck wrote:
>
>> On 09/19/2016 02:11 AM, Stafford Horne wrote:
>>>
>>>
>>>  On Mon, 19 Sep 2016, Guenter Roeck wrote:
>>>
>>> >  On 09/18/2016 11:02 PM, Stafford Horne wrote:
>>> > > > > > >   On Sun, 18 Sep 2016, Guenter Roeck wrote:
>>> > > > > >   Tested-by: Guenter Roeck <linux@roeck-us.net>
>>> > > > >   If you plan to handle openrisc going forward, it would be great > > > >   if you >  could
>>> > > >   consider updating MAINTAINERS. The web site and git repository have > > >   been >  unreachable
>>> > > >   for a long time.
>>> > > > >   Thank you,
>>> > >   Updating maintainers was kind of on my plans, but I figured I need to
>>> > >   prove that I kind of know what I am doing.
>>> > > > >  The alternative would be to mark it as Orphaned. Which, for all >  practical purpose,
>>> >  would be the correct state right now.
>>>
>>>  +CC The openrisc list
>>>
>>>  Understood, I don't think we would want that to happen.
>>>
>> Look at the entry today:
>>
>> OPENRISC ARCHITECTURE
>> M:      Jonas Bonn <jonas@southpole.se>
>> W:      http://openrisc.net
>> S:      Maintained
>> T:      git git://openrisc.net/~jonas/linux
>> F:      arch/openrisc/
>>
>> At the very least, W: and T: are incorrect and need to be updated or removed.
>> Plus, apparently there is a L:, and "T: https://github.com/openrisc/linux"
>> might be appropriate.
>>
>
> Thanks,
> I am aware of this, we have since setup a new website, mailing list and as you have found, git repo. Stefan has been nominated as the maintainer by Jonas on a previous mail thread.
>
> The issue (as we see it) is that neither Stefan or I have signed PGP keys by anyone in the web of trust.
>
> I sent this patch set with a cover lett trying to explain of the situation trying to get some help.  Your reponses are very helpful.
>
> Do you think I should just send "git pull" reuqests to Linus with a self signed pgp key and eplaination to see how it goes?
>

Nope, that won't work. Linus will not accept pull requests without signed key,
or at least I would be very surprised if he does. You'll have to get your key
signed. I understand that may be tricky, with you being in Japan (if that is
you ;-), but we can't help it.

Guenter

> -Stafford
>
> FYI
> I have a change as following in my backlog, as follows:
>
> ---
> @@ -8691,10 +8063,12 @@ F:      drivers/of/overlay.c
>  F:     drivers/of/resolver.c
>
>  OPENRISC ARCHITECTURE
> -M:    Jonas Bonn <jonas@southpole.se>
> -W:    http://openrisc.net
> +M:    Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
> +M:    Stafford Horne <shorne@gmail.com>
> +W:    http://openrisc.io
> +L:    openrisc at lists.librecores.org
> +T:    https://github.com/openrisc/linux.git
>  S:    Maintained
> -T:    git git://openrisc.net/~jonas/linux
>  F:    arch/openrisc/
>
>  OPENVSWITCH
>
> --
>

[OpenRISC] [PATCH 5/7] openrisc: Support both old (or32) and new (or1k) toolchain

[Guenter Roeck]

On 09/19/2016 07:35 AM, Jonas Bonn wrote:
> On 09/19/2016 04:04 PM, Stafford Horne wrote:
>>
>>
>> On Mon, 19 Sep 2016, Guenter Roeck wrote:
>>
>>> On 09/19/2016 02:11 AM, Stafford Horne wrote:
>>>>
>>>>
>>>>  On Mon, 19 Sep 2016, Guenter Roeck wrote:
>>>>
>>>> >  On 09/18/2016 11:02 PM, Stafford Horne wrote:
>>>> > > > > > >   On Sun, 18 Sep 2016, Guenter Roeck wrote:
>>>> > > > > >   Tested-by: Guenter Roeck <linux@roeck-us.net>
>>>> > > > >   If you plan to handle openrisc going forward, it would be great > > > >   if you > could
>>>> > > >   consider updating MAINTAINERS. The web site and git repository have > > >   been > unreachable
>>>> > > >   for a long time.
>>>> > > > >   Thank you,
>>>> > >   Updating maintainers was kind of on my plans, but I figured I need to
>>>> > >   prove that I kind of know what I am doing.
>>>> > > > >  The alternative would be to mark it as Orphaned. Which, for all >  practical purpose,
>>>> >  would be the correct state right now.
>>>>
>>>>  +CC The openrisc list
>>>>
>>>>  Understood, I don't think we would want that to happen.
>>>>
>>> Look at the entry today:
>>>
>>> OPENRISC ARCHITECTURE
>>> M:      Jonas Bonn <jonas@southpole.se>
>>> W:      http://openrisc.net
>>> S:      Maintained
>>> T:      git git://openrisc.net/~jonas/linux
>>> F:      arch/openrisc/
>>>
>>> At the very least, W: and T: are incorrect and need to be updated or removed.
>>> Plus, apparently there is a L:, and "T: https://github.com/openrisc/linux"
>>> might be appropriate.
>>>
>>
>> Thanks,
>> I am aware of this, we have since setup a new website, mailing list and as you have found, git repo. Stefan has been nominated as the maintainer by Jonas on a previous mail thread.
>>
>> The issue (as we see it) is that neither Stefan or I have signed PGP keys by anyone in the web of trust.
>>
>> I sent this patch set with a cover lett trying to explain of the situation trying to get some help.  Your reponses are very helpful.
>>
>> Do you think I should just send "git pull" reuqests to Linus with a self signed pgp key and eplaination to see how it goes?
>
> The bigger question I would have at this point is the value of the code remaining upstream...  Five years ago, there was a promise to try to get the toolchain upstream within a year or two; to this day, I don't know that much progress has been made there so this architecture still requires a hodge-podge of tools from various sources to build.
>
> Given the toolchain maintainer's general reluctance to move things upstream, I'd almost be inclined to just remove the OpenRISC arch from the kernel altogether.  Are there any other arch's that can't be built with an upstream GCC at this point?
>

Yes, several. Definitely avr32. Several others don't build with the upstream gcc,
but no one really cares enough to fix it.

Guenter

> /Jonas
>
>>
>> -Stafford
>>
>> FYI
>> I have a change as following in my backlog, as follows:
>>
>> ---
>> @@ -8691,10 +8063,12 @@ F:      drivers/of/overlay.c
>>  F:     drivers/of/resolver.c
>>
>>  OPENRISC ARCHITECTURE
>> -M:    Jonas Bonn <jonas@southpole.se>
>> -W:    http://openrisc.net
>> +M:    Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
>> +M:    Stafford Horne <shorne@gmail.com>
>> +W:    http://openrisc.io
>> +L:    openrisc at lists.librecores.org
>> +T:    https://github.com/openrisc/linux.git
>>  S:    Maintained
>> -T:    git git://openrisc.net/~jonas/linux
>>  F:    arch/openrisc/
>>
>>  OPENVSWITCH
>>
>> --
>
>

[OpenRISC] [PATCH 5/7] openrisc: Support both old (or32) and new (or1k) toolchain

[Stefan Wallentowitz]

On 19.09.2016 16:35, Jonas Bonn wrote:

> The bigger question I would have at this point is the value of the code
> remaining upstream...  Five years ago, there was a promise to try to get
> the toolchain upstream within a year or two; to this day, I don't know
> that much progress has been made there so this architecture still
> requires a hodge-podge of tools from various sources to build.

Actually, there has been progress. All but one copyright assignment have
been collected and the last one blocks everything. Don't know if there
was any progress on this since last ORCONF, but at least we have like
nearly up-to-date GCC for some time now.

Cheers,
Stefan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.librecores.org/pipermail/openrisc/attachments/20160919/26acad3b/attachment.sig>

[OpenRISC] [PATCH 5/7] openrisc: Support both old (or32) and new (or1k) toolchain

[Stefan Wallentowitz]

On 19.09.2016 16:35, Jonas Bonn wrote:

> The bigger question I would have at this point is the value of the code
> remaining upstream...  Five years ago, there was a promise to try to get
> the toolchain upstream within a year or two; to this day, I don't know
> that much progress has been made there so this architecture still
> requires a hodge-podge of tools from various sources to build.

Actually, there has been progress. All but one copyright assignment have
been collected and the last one blocks everything. Don't know if there
was any progress on this since last ORCONF, but at least we have like
nearly up-to-date GCC for some time now.

Cheers,
Stefan



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.librecores.org/pipermail/openrisc/attachments/20160919/e77b16bd/attachment.sig>

[OpenRISC] [PATCH 5/7] openrisc: Support both old (or32) and new (or1k) toolchain

[Stafford Horne]

On Mon, 19 Sep 2016, Jonas Bonn wrote:

> On 09/19/2016 04:04 PM, Stafford Horne wrote:
>> 
>>
>>  On Mon, 19 Sep 2016, Guenter Roeck wrote:
>> 
>> >  On 09/19/2016 02:11 AM, Stafford Horne wrote:
>> > > 
>> > > 
>> > >   On Mon, 19 Sep 2016, Guenter Roeck wrote:
>> > > 
>> > > >   On 09/18/2016 11:02 PM, Stafford Horne wrote:
>> > > > > > > > >    On Sun, 18 Sep 2016, Guenter Roeck wrote:
>> > > > > > > >    Tested-by: Guenter Roeck <linux@roeck-us.net>
>> > > > > > >    If you plan to handle openrisc going forward, it would be 
>> > > great > > > >    if you > could
>> > > > > >    consider updating MAINTAINERS. The web site and git 
>> > >  repository have > > >   been > unreachable
>> > > > > >    for a long time.
>> > > > > > >    Thank you,
>> > > > >    Updating maintainers was kind of on my plans, but I figured I 
>> > >  need to
>> > > > >    prove that I kind of know what I am doing.
>> > > > > > >   The alternative would be to mark it as Orphaned. Which, for 
>> > > all >   practical purpose,
>> > > >   would be the correct state right now.
>> > > 
>> > >   +CC The openrisc list
>> > > 
>> > >   Understood, I don't think we would want that to happen.
>> > > 
>> >  Look at the entry today:
>> > 
>> >  OPENRISC ARCHITECTURE
>> >  M:      Jonas Bonn <jonas@southpole.se>
>> >  W:      http://openrisc.net
>> >  S:      Maintained
>> >  T:      git git://openrisc.net/~jonas/linux
>> >  F:      arch/openrisc/
>> > 
>> >  At the very least, W: and T: are incorrect and need to be updated or 
>> >  removed.
>> >  Plus, apparently there is a L:, and "T: 
>> >  https://github.com/openrisc/linux"
>> >  might be appropriate.
>> > 
>>
>>  Thanks,
>>  I am aware of this, we have since setup a new website, mailing list and as
>>  you have found, git repo. Stefan has been nominated as the maintainer by
>>  Jonas on a previous mail thread.
>>
>>  The issue (as we see it) is that neither Stefan or I have signed PGP keys
>>  by anyone in the web of trust.
>>
>>  I sent this patch set with a cover lett trying to explain of the situation
>>  trying to get some help.  Your reponses are very helpful.
>>
>>  Do you think I should just send "git pull" reuqests to Linus with a self
>>  signed pgp key and eplaination to see how it goes?
>
> The bigger question I would have at this point is the value of the code 
> remaining upstream...  Five years ago, there was a promise to try to get the 
> toolchain upstream within a year or two; to this day, I don't know that much 
> progress has been made there so this architecture still requires a 
> hodge-podge of tools from various sources to build.
>
> Given the toolchain maintainer's general reluctance to move things upstream, 
> I'd almost be inclined to just remove the OpenRISC arch from the kernel 
> altogether.  Are there any other arch's that can't be built with an upstream 
> GCC at this point?

Hi Jonas,
We have tried to get the toolchain in order in the last year.  The latest 
efforts is headlined by a toolchain build tutorial here:
   http://openrisc.io/newlib/building.html

The main toolchain project
  binutils-gdb - is upstreamed, I have been working on getting more of the
                 but there are many patches sitting in our repo on github
                 I have been working on getting them rebased to 7.11 and
                 upstreamed.
  newlib       - is upstreamed, with my gdb fixes I have also worked on
                 fixing some bugs in the last year.
  gcc          - this is the problem, the gcc code has not been signed over
                 to the fsf by the original authors.  A clean-room rewrite
                 seems to needed last I checked

The projects are all being maintained on the openrisc github page and we 
are trying to keep it going.

The attraction of openrisc, I would say, is that its one of the only fully 
open platforms in the kernel. Its also relatively simple so for hobbyist 
and students who want to have a 32-bit cpu which they can do 'full-stack' 
development on it fits a good nitch.

Keeping it upstream means also this code base is not getting stale. But we 
do need people to look after it and the patches.

-Stafford

>>
>>  -Stafford
>>
>>  FYI
>>  I have a change as following in my backlog, as follows:
>>
>>  ---
>>  @@ -8691,10 +8063,12 @@ F:      drivers/of/overlay.c
>>   F:     drivers/of/resolver.c
>>
>>  OPENRISC ARCHITECTURE
>>  -M:    Jonas Bonn <jonas@southpole.se>
>>  -W:    http://openrisc.net
>>  +M:    Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
>>  +M:    Stafford Horne <shorne@gmail.com>
>>  +W:    http://openrisc.io
>>  +L:    openrisc at lists.librecores.org
>>  +T:    https://github.com/openrisc/linux.git
>>  S:    Maintained
>>  -T:    git git://openrisc.net/~jonas/linux
>>   F:    arch/openrisc/
>>
>>   OPENVSWITCH
>>
>>  -- 
>
>

[OpenRISC] [PATCH 5/7] openrisc: Support both old (or32) and new (or1k) toolchain

[Jeremy Bennett]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 19/09/16 15:58, Stefan Wallentowitz wrote:
> On 19.09.2016 16:35, Jonas Bonn wrote:
> 
>> The bigger question I would have at this point is the value of
>> the code remaining upstream...  Five years ago, there was a
>> promise to try to get the toolchain upstream within a year or
>> two; to this day, I don't know that much progress has been made
>> there so this architecture still requires a hodge-podge of tools
>> from various sources to build.
> 
> Actually, there has been progress. All but one copyright assignment
> have been collected and the last one blocks everything. Don't know
> if there was any progress on this since last ORCONF, but at least
> we have like nearly up-to-date GCC for some time now.

Is there anything I can do to help unblock the last one (having been
around longer than some, I know some of the old contributors).

Best wishes,


Jeremy

> 
> Cheers, Stefan
> 
> 
> 
> _______________________________________________ OpenRISC mailing
> list OpenRISC at lists.librecores.org 
> https://lists.librecores.org/listinfo/openrisc
> 


- -- 
Tel:     +44 (1590) 610184
Cell:    +44 (7970) 676050
SkypeID: jeremybennett
Twitter: @jeremypbennett
Email:   jeremy.bennett at embecosm.com
Web:     www.embecosm.com
PGP key: 1024D/BEF58172FB4754E1 2009-03-20
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iGMEARECACMFAlfgBfIcHGplcmVteS5iZW5uZXR0QGVtYmVjb3NtLmNvbQAKCRC+
9YFy+0dU4fbcAKCBzSWPJ1diLz+0SLg4CpEwqBzOoACdF0y4LSTM/vBsqEFVDWN/
nnkYeZ8=
=52x5
-----END PGP SIGNATURE-----

[OpenRISC] [PATCH 5/7] openrisc: Support both old (or32) and new (or1k) toolchain

[Stafford Horne]

On Mon, 19 Sep 2016, Jeremy Bennett wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 19/09/16 15:58, Stefan Wallentowitz wrote:
>> On 19.09.2016 16:35, Jonas Bonn wrote:
>> 
>>> The bigger question I would have at this point is the value of
>>> the code remaining upstream...  Five years ago, there was a
>>> promise to try to get the toolchain upstream within a year or
>>> two; to this day, I don't know that much progress has been made
>>> there so this architecture still requires a hodge-podge of tools
>>> from various sources to build.
>> 
>> Actually, there has been progress. All but one copyright assignment
>> have been collected and the last one blocks everything. Don't know
>> if there was any progress on this since last ORCONF, but at least
>> we have like nearly up-to-date GCC for some time now.
>
> Is there anything I can do to help unblock the last one (having been
> around longer than some, I know some of the old contributors).

Hi Jeremy,

As far as I can tell from SVN->Git history, the first changes I can see 
are from "Giuseppe Scrivano" and "Peter Gavin" back in 2011.  I am 
guessing the fsf assignments are in order with them.

I would think that the one that Stefan mentioned is missing is *Damjan* 
who started port. Are you in contact with him?

https://gcc.gnu.org/ml/gcc/1999-11n/msg00391.html - first contact with gcc

https://gcc.gnu.org/ml/gcc-patches/2002-02/msg01788.html - further 
discussions

I would leave it to Stefan for details.

>> _______________________________________________ OpenRISC mailing
>> list OpenRISC at lists.librecores.org 
>> https://lists.librecores.org/listinfo/openrisc
>> 
>
>
> - -- 
> Tel:     +44 (1590) 610184
> Cell:    +44 (7970) 676050
> SkypeID: jeremybennett
> Twitter: @jeremypbennett
> Email:   jeremy.bennett at embecosm.com
> Web:     www.embecosm.com
> PGP key: 1024D/BEF58172FB4754E1 2009-03-20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iGMEARECACMFAlfgBfIcHGplcmVteS5iZW5uZXR0QGVtYmVjb3NtLmNvbQAKCRC+
> 9YFy+0dU4fbcAKCBzSWPJ1diLz+0SLg4CpEwqBzOoACdF0y4LSTM/vBsqEFVDWN/
> nnkYeZ8=
> =52x5
> -----END PGP SIGNATURE-----
> _______________________________________________
> OpenRISC mailing list
> OpenRISC at lists.librecores.org
> https://lists.librecores.org/listinfo/openrisc

[OpenRISC] [PATCH 5/7] openrisc: Support both old (or32) and new (or1k) toolchain

[Jeremy Bennett]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 19/09/16 17:09, Stafford Horne wrote:
> 
> 
> On Mon, 19 Sep 2016, Jeremy Bennett wrote:
> 
> On 19/09/16 15:58, Stefan Wallentowitz wrote:
>>>> On 19.09.2016 16:35, Jonas Bonn wrote:
>>>> 
>>>>> The bigger question I would have at this point is the value
>>>>> of the code remaining upstream...  Five years ago, there
>>>>> was a promise to try to get the toolchain upstream within a
>>>>> year or two; to this day, I don't know that much progress
>>>>> has been made there so this architecture still requires a
>>>>> hodge-podge of tools from various sources to build.
>>>> 
>>>> Actually, there has been progress. All but one copyright
>>>> assignment have been collected and the last one blocks
>>>> everything. Don't know if there was any progress on this
>>>> since last ORCONF, but at least we have like nearly
>>>> up-to-date GCC for some time now.
> 
> Is there anything I can do to help unblock the last one (having
> been around longer than some, I know some of the old
> contributors).
> 
>> Hi Jeremy,
> 
>> As far as I can tell from SVN->Git history, the first changes I
>> can see are from "Giuseppe Scrivano" and "Peter Gavin" back in
>> 2011.  I am guessing the fsf assignments are in order with them.
> 
>> I would think that the one that Stefan mentioned is missing is
>> *Damjan* who started port. Are you in contact with him?

Hi Stafford,

I haven't seen him for some years, but I'm connected on LinkedIn. I
can ping him.

I presume you would like him to assign any copyright in the GNU tool
chain for OpenRISC?

Best wishes,


Jeremy

>> https://gcc.gnu.org/ml/gcc/1999-11n/msg00391.html - first contact
>> with gcc
> 
>> https://gcc.gnu.org/ml/gcc-patches/2002-02/msg01788.html -
>> further discussions
> 
>> I would leave it to Stefan for details.
> 
>>>> _______________________________________________ OpenRISC
>>>> mailing list OpenRISC at lists.librecores.org 
>>>> https://lists.librecores.org/listinfo/openrisc
>>>> 
> 
> 
> -- Tel:     +44 (1590) 610184 Cell:    +44 (7970) 676050 SkypeID:
> jeremybennett Twitter: @jeremypbennett Email:
> jeremy.bennett at embecosm.com Web:     www.embecosm.com PGP key:
> 1024D/BEF58172FB4754E1 2009-03-20
>> _______________________________________________ OpenRISC mailing
>> list OpenRISC at lists.librecores.org 
>> https://lists.librecores.org/listinfo/openrisc

- -- 
Tel:     +44 (1590) 610184
Cell:    +44 (7970) 676050
SkypeID: jeremybennett
Twitter: @jeremypbennett
Email:   jeremy.bennett at embecosm.com
Web:     www.embecosm.com
PGP key: 1024D/BEF58172FB4754E1 2009-03-20
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iGMEARECACMFAlfgEeYcHGplcmVteS5iZW5uZXR0QGVtYmVjb3NtLmNvbQAKCRC+
9YFy+0dU4crgAKCTurydEQd1fKESpyf2ax2JmtB5RACfeyjovCkmP3P9MJXnCJ4u
SM0RDa8=
=sPoa
-----END PGP SIGNATURE-----

[OpenRISC] [PATCH 5/7] openrisc: Support both old (or32) and new (or1k) toolchain

[Stefan Wallentowitz]

I think it was beyond semi that are missing. 

Cheers, 
Stefan 

On September 19, 2016 6:27:19 PM GMT+02:00, Jeremy Bennett <jeremy.bennett@embecosm.com> wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>On 19/09/16 17:09, Stafford Horne wrote:
>> 
>> 
>> On Mon, 19 Sep 2016, Jeremy Bennett wrote:
>> 
>> On 19/09/16 15:58, Stefan Wallentowitz wrote:
>>>>> On 19.09.2016 16:35, Jonas Bonn wrote:
>>>>> 
>>>>>> The bigger question I would have at this point is the value
>>>>>> of the code remaining upstream...  Five years ago, there
>>>>>> was a promise to try to get the toolchain upstream within a
>>>>>> year or two; to this day, I don't know that much progress
>>>>>> has been made there so this architecture still requires a
>>>>>> hodge-podge of tools from various sources to build.
>>>>> 
>>>>> Actually, there has been progress. All but one copyright
>>>>> assignment have been collected and the last one blocks
>>>>> everything. Don't know if there was any progress on this
>>>>> since last ORCONF, but at least we have like nearly
>>>>> up-to-date GCC for some time now.
>> 
>> Is there anything I can do to help unblock the last one (having
>> been around longer than some, I know some of the old
>> contributors).
>> 
>>> Hi Jeremy,
>> 
>>> As far as I can tell from SVN->Git history, the first changes I
>>> can see are from "Giuseppe Scrivano" and "Peter Gavin" back in
>>> 2011.  I am guessing the fsf assignments are in order with them.
>> 
>>> I would think that the one that Stefan mentioned is missing is
>>> *Damjan* who started port. Are you in contact with him?
>
>Hi Stafford,
>
>I haven't seen him for some years, but I'm connected on LinkedIn. I
>can ping him.
>
>I presume you would like him to assign any copyright in the GNU tool
>chain for OpenRISC?
>
>Best wishes,
>
>
>Jeremy
>
>>> https://gcc.gnu.org/ml/gcc/1999-11n/msg00391.html - first contact
>>> with gcc
>> 
>>> https://gcc.gnu.org/ml/gcc-patches/2002-02/msg01788.html -
>>> further discussions
>> 
>>> I would leave it to Stefan for details.
>> 
>>>>> _______________________________________________ OpenRISC
>>>>> mailing list OpenRISC at lists.librecores.org 
>>>>> https://lists.librecores.org/listinfo/openrisc
>>>>> 
>> 
>> 
>> -- Tel:     +44 (1590) 610184 Cell:    +44 (7970) 676050 SkypeID:
>> jeremybennett Twitter: @jeremypbennett Email:
>> jeremy.bennett at embecosm.com Web:     www.embecosm.com PGP key:
>> 1024D/BEF58172FB4754E1 2009-03-20
>>> _______________________________________________ OpenRISC mailing
>>> list OpenRISC at lists.librecores.org 
>>> https://lists.librecores.org/listinfo/openrisc
>
>- -- 
>Tel:     +44 (1590) 610184
>Cell:    +44 (7970) 676050
>SkypeID: jeremybennett
>Twitter: @jeremypbennett
>Email:   jeremy.bennett at embecosm.com
>Web:     www.embecosm.com
>PGP key: 1024D/BEF58172FB4754E1 2009-03-20
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v2
>
>iGMEARECACMFAlfgEeYcHGplcmVteS5iZW5uZXR0QGVtYmVjb3NtLmNvbQAKCRC+
>9YFy+0dU4crgAKCTurydEQd1fKESpyf2ax2JmtB5RACfeyjovCkmP3P9MJXnCJ4u
>SM0RDa8=
>=sPoa
>-----END PGP SIGNATURE-----
>_______________________________________________
>OpenRISC mailing list
>OpenRISC at lists.librecores.org
>https://lists.librecores.org/listinfo/openrisc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.librecores.org/pipermail/openrisc/attachments/20160919/33e4c201/attachment.html>

[OpenRISC] [PATCH 5/7] openrisc: Support both old (or32) and new (or1k) toolchain

[Jeremy Bennett]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 19/09/16 18:15, Stefan Wallentowitz wrote:
> I think it was beyond semi that are missing.

I can't help there - I don't have the necessary relationships.  Might
be worth checking if the key players already have assignments on file
at the FSF.  If Damjan has, so may the others from the same time.

Best wishes,


Jeremy

> 
> Cheers, Stefan
> 
> On September 19, 2016 6:27:19 PM GMT+02:00, Jeremy Bennett 
> <jeremy.bennett@embecosm.com> wrote:
> 
> On 19/09/16 17:09, Stafford Horne wrote:
> 
> 
> 
> On Mon, 19 Sep 2016, Jeremy Bennett wrote:
> 
> On 19/09/16 15:58, Stefan Wallentowitz wrote:
> 
> On 19.09.2016 16:35, Jonas Bonn wrote:
> 
> The bigger question I would have at this point is the value of the
> code remaining upstream... Five years ago, there was a promise to
> try to get the toolchain upstream within a year or two; to this
> day, I don't know that much progress has been made there so this
> architecture still requires a hodge-podge of tools from various
> sources to build.
> 
> 
> Actually, there has been progress. All but one copyright assignment
> have been collected and the last one blocks everything. Don't know
> if there was any progress on this since last ORCONF, but at least
> we have like nearly up-to-date GCC for some time now.
> 
> 
> Is there anything I can do to help unblock the last one (having 
> been around longer than some, I know some of the old 
> contributors).
> 
> Hi Jeremy,
> 
> 
> As far as I can tell from SVN->Git history, the first changes I can
> see are from "Giuseppe Scrivano" and "Peter Gavin" back in 2011. I
> am guessing the fsf assignments are in order with them.
> 
> 
> I would think that the one that Stefan mentioned is missing is 
> *Damjan* who started port. Are you in contact with him?
> 
> 
> Hi Stafford,
> 
> I haven't seen him for some years, but I'm connected on LinkedIn.
> I can ping him.
> 
> I presume you would like him to assign any copyright in the GNU
> tool chain for OpenRISC?
> 
> Best wishes,
> 
> 
> Jeremy
> 
> https://gcc.gnu.org/ml/gcc/1999-11n/msg00391.html - first contact 
> with gcc
> 
> 
> https://gcc.gnu.org/ml/gcc-patches/2002-02/msg01788.html - further
> discussions
> 
> 
> I would leave it to Stefan for details.
> 
> 
> ------------------------------------------------------------------------
>
> 
OpenRISC
> mailing list OpenRISC at lists.librecores.org 
> https://lists.librecores.org/listinfo/openrisc
> 
> 
> 
> -- Tel: +44 (1590) 610184 Cell: +44 (7970) 676050 SkypeID: 
> jeremybennett Twitter: @jeremypbennett Email: 
> jeremy.bennett at embecosm.com Web: www.embecosm.com 
> <http://www.embecosm.com> PGP key: 1024D/BEF58172FB4754E1
> 2009-03-20
> 
> ------------------------------------------------------------------------
>
> 
OpenRISC mailing
> list OpenRISC at lists.librecores.org 
> https://lists.librecores.org/listinfo/openrisc
> 
> 
> ------------------------------------------------------------------------
>
>  OpenRISC mailing list OpenRISC at lists.librecores.org 
> https://lists.librecores.org/listinfo/openrisc
> 

- -- 
Tel:     +44 (1590) 610184
Cell:    +44 (7970) 676050
SkypeID: jeremybennett
Twitter: @jeremypbennett
Email:   jeremy.bennett at embecosm.com
Web:     www.embecosm.com
PGP key: 1024D/BEF58172FB4754E1 2009-03-20
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iGMEARECACMFAlfgJTAcHGplcmVteS5iZW5uZXR0QGVtYmVjb3NtLmNvbQAKCRC+
9YFy+0dU4V9jAJ0bR6s/YiHWCEBalLOKBW/gO6KDLwCfeHgL3PnSsJTWKNvVI+CD
ncDO268=
=wMBt
-----END PGP SIGNATURE-----

[OpenRISC] [PATCH 5/7] openrisc: Support both old (or32) and new (or1k) toolchain

[Stafford Horne]

On Mon, 19 Sep 2016, Guenter Roeck wrote:

> On 09/19/2016 07:04 AM, Stafford Horne wrote:
>> 
>>
>>  On Mon, 19 Sep 2016, Guenter Roeck wrote:
>> 
>> >  On 09/19/2016 02:11 AM, Stafford Horne wrote:
>> > > 
>> > > 
>> > >   On Mon, 19 Sep 2016, Guenter Roeck wrote:
>> > > 
>> > > >   On 09/18/2016 11:02 PM, Stafford Horne wrote:
>> > > > > > > > >    On Sun, 18 Sep 2016, Guenter Roeck wrote:
>> > > > > > > >    Tested-by: Guenter Roeck <linux@roeck-us.net>
>> > > > > > >    If you plan to handle openrisc going forward, it would be 
>> > > > > > >    great > > > >   if you >  could
>> > > > > >    consider updating MAINTAINERS. The web site and git repository 
>> > > > > >    have > > >   been >  unreachable
>> > > > > >    for a long time.
>> > > > > > >    Thank you,
>> > > > >    Updating maintainers was kind of on my plans, but I figured I 
>> > > > >    need to
>> > > > >    prove that I kind of know what I am doing.
>> > > > > > >   The alternative would be to mark it as Orphaned. Which, for 
>> > > > > > >   all >  practical purpose,
>> > > >   would be the correct state right now.
>> > > 
>> > >   +CC The openrisc list
>> > > 
>> > >   Understood, I don't think we would want that to happen.
>> > > 
>> >  Look at the entry today:
>> > 
>> >  OPENRISC ARCHITECTURE
>> >  M:      Jonas Bonn <jonas@southpole.se>
>> >  W:      http://openrisc.net
>> >  S:      Maintained
>> >  T:      git git://openrisc.net/~jonas/linux
>> >  F:      arch/openrisc/
>> > 
>> >  At the very least, W: and T: are incorrect and need to be updated or 
>> >  removed.
>> >  Plus, apparently there is a L:, and "T: 
>> >  https://github.com/openrisc/linux"
>> >  might be appropriate.
>> > 
>>
>>  Thanks,
>>  I am aware of this, we have since setup a new website, mailing list and as
>>  you have found, git repo. Stefan has been nominated as the maintainer by
>>  Jonas on a previous mail thread.
>>
>>  The issue (as we see it) is that neither Stefan or I have signed PGP keys
>>  by anyone in the web of trust.
>>
>>  I sent this patch set with a cover lett trying to explain of the situation
>>  trying to get some help.  Your reponses are very helpful.
>>
>>  Do you think I should just send "git pull" reuqests to Linus with a self
>>  signed pgp key and eplaination to see how it goes?
>> 
>
> Nope, that won't work. Linus will not accept pull requests without signed 
> key,
> or at least I would be very surprised if he does. You'll have to get your key
> signed. I understand that may be tricky, with you being in Japan (if that is
> you ;-), but we can't help it.

Thats as I figured.

It is me and I just missed LinuxCon Japan 2016 as I was out of town. I 
have some contacts I may be able to reach out to though.

-Stafford

>>  FYI
>>  I have a change as following in my backlog, as follows:
>>
>>  ---
>>  @@ -8691,10 +8063,12 @@ F:      drivers/of/overlay.c
>>   F:     drivers/of/resolver.c
>>
>>  OPENRISC ARCHITECTURE
>>  -M:    Jonas Bonn <jonas@southpole.se>
>>  -W:    http://openrisc.net
>>  +M:    Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
>>  +M:    Stafford Horne <shorne@gmail.com>
>>  +W:    http://openrisc.io
>>  +L:    openrisc at lists.librecores.org
>>  +T:    https://github.com/openrisc/linux.git
>>  S:    Maintained
>>  -T:    git git://openrisc.net/~jonas/linux
>>   F:    arch/openrisc/
>>
>>   OPENVSWITCH
>>
>>  --
>> 
>
>