Re: [ORLinux] [PATCH] openrisc: Add DTS and defconfig for DE0-Nano

[Olof Kindgren]

2013/11/16 Stefan Kristiansson 
>
> On Fri, Nov 15, 2013 at 10:50:18AM +0100, Jonas Bonn wrote:
> > >+
> > >+i2c0: ocores@a000 {
> > >+#address-cells = <1>;
> > >+#size-cells = <0>;
> > >+compatible = "opencores,i2c-ocores";
> >
> > Version number needed.  OpenCores wanted "projectname-rtlsvn###"
> > where ### is the SVN commit number of the RTL directory in the
> > project's source repository.
> >
>
> That will also require a change to the driver.
>
> Using svn commit ids as version info seems a bit too fine grained to me,
> but if that's what's agreed on, then it should be the commit id from the
> projects official repository at opencores.org I think.
>
> Stefan
> ___
> Linux mailing list
> li...@lists.openrisc.net
> http://lists.openrisc.net/listinfo/linux


I agree. I don't like doing versioning with revision numbers. It's too
closely tied to the currently used VCS. The problem is that no one has
bothered to do proper releases of the cores for the last ten years or
so.

But since we are talking about a relatively small amount of cores
here, I think it could be worth to take a quick glance to see if the
latest SVN version is compatible with the latest tagged release. I
would suspect that is the case for the majority of the cores and the
we can just use the latest tag as version. For the other cores we
could
1. Use latest tag + 1 (a bit ugly if the maintainer wants to do a proper release
2. Take over maintainership/fork and just release what's in the trunk
(taking over maintenance is preferrable here to avoid  more repo
confusion)
3. Use SVN revisions

option 2 would be my preferred choice here, given that we get someone
to do the actual work. I could probably help out with a few of the
cores

Jonas, you said that opencores wanted projectname-svnversion. Do you
know where that comes from? My proposal here would conflict with that

//Olof
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: [OpenRISC] [PATCH v2 8/9] openrisc: Updates after openrisc.net has been lost

[Olof Kindgren]

On Mon, Nov 14, 2016 at 2:30 PM, Stafford Horne  wrote:
> The openrisc.net domain expired and was taken over by squatters.
> These updates point documentation to the new domain, mailing lists
> and git repos.
>
> Also, Jonas is not the main maintainer anylonger, he reviews changes
> but does not maintain a repo or sent pull requests.  Updating this to
> add Stafford and Stefan who are the active maintainers.
>
> Signed-off-by: Stafford Horne 
> ---
>  MAINTAINERS   | 6 --
>  arch/openrisc/README.openrisc | 8 
>  arch/openrisc/kernel/setup.c  | 2 +-
>  3 files changed, 9 insertions(+), 7 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 851b89b..d84a585 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -8958,9 +8958,11 @@ F:   drivers/of/resolver.c
>
>  OPENRISC ARCHITECTURE
>  M: Jonas Bonn 
> -W: http://openrisc.net
> +M: Stefan Kristiansson 
> +M: Stafford Horne 
> +L: openr...@lists.librecores.org
> +W: http://openrisc.io
>  S: Maintained
> -T: git git://openrisc.net/~jonas/linux
>  F: arch/openrisc/
>
>  OPENVSWITCH
> diff --git a/arch/openrisc/README.openrisc b/arch/openrisc/README.openrisc
> index c9f7edf..072069a 100644
> --- a/arch/openrisc/README.openrisc
> +++ b/arch/openrisc/README.openrisc
> @@ -6,7 +6,7 @@ target architecture, specifically, is the 32-bit OpenRISC 
> 1000 family (or1k).
>
>  For information about OpenRISC processors and ongoing development:
>
> -   website http://openrisc.net
> +   website http://openrisc.io
>
>  For more information about Linux on OpenRISC, please contact South Pole AB.
>
> @@ -24,17 +24,17 @@ In order to build and run Linux for OpenRISC, you'll need 
> at least a basic
>  toolchain and, perhaps, the architectural simulator.  Steps to get these bits
>  in place are outlined here.
>
> -1)  The toolchain can be obtained from openrisc.net.  Instructions for 
> building
> +1)  The toolchain can be obtained from openrisc.io.  Instructions for 
> building
>  a toolchain can be found at:
>
> -http://openrisc.net/toolchain-build.html
> +https://github.com/openrisc/tutorials
>
>  2) or1ksim (optional)
>
>  or1ksim is the architectural simulator which will allow you to actually run
>  your OpenRISC Linux kernel if you don't have an OpenRISC processor at hand.
>
> -   git clone git://openrisc.net/jonas/or1ksim-svn
> +   git clone https://github.com/openrisc/or1ksim.git
>
> cd or1ksim
> ./configure --prefix=$OPENRISC_PREFIX
> diff --git a/arch/openrisc/kernel/setup.c b/arch/openrisc/kernel/setup.c
> index 6329d7a..cb797a3 100644
> --- a/arch/openrisc/kernel/setup.c
> +++ b/arch/openrisc/kernel/setup.c
> @@ -295,7 +295,7 @@ void __init setup_arch(char **cmdline_p)
>
> *cmdline_p = boot_command_line;
>
> -   printk(KERN_INFO "OpenRISC Linux -- http://openrisc.net\n";);
> +   printk(KERN_INFO "OpenRISC Linux -- http://openrisc.io\n";);
>  }
>
>  static int show_cpuinfo(struct seq_file *m, void *v)
> --
> 2.7.4
>
> ___
> OpenRISC mailing list
> openr...@lists.librecores.org
> https://lists.librecores.org/listinfo/openrisc

This looks all correct
Acked-by: Olof Kindgren