devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonas Bonn <jonas@southpole.se>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Kevin Mehall <contact@kevinmehall.net>,
	linux@lists.openrisc.net
Subject: Re: [PATCH] openrisc: Add DTS and defconfig for DE0-Nano
Date: Fri, 15 Nov 2013 11:57:33 +0100	[thread overview]
Message-ID: <5285FE1D.3020800@southpole.se> (raw)
In-Reply-To: <CAMuHMdWA-9ax=NG_d0tyfzY3+42Ka7_r+jTeF-m5oW0eV8t1=g@mail.gmail.com>

On 11/15/2013 11:22 AM, Geert Uytterhoeven wrote:
>> This should probably be "altera,de0_nano".  We also need to put a version
>
> "terasic,de0_nano"? The board says "Designed and manufactured by Terasic".
> Hmm, the sticker on the box says "Altera DE0-Nano".

Good question...

>>
>> Version number needed.  OpenCores wanted "projectname-rtlsvn###" where ###
>> is the SVN commit number of the RTL directory in the project's source
>> repository.
>
> That's gonna need some information diving, as Stefan's orpsoc git repositories
> only contains references to orpsocv2 git-svn-ids, not the svn ids of
> the original
> component repositories.

Stefan?  Where's the "official" home of these cores nowadays?  Have they 
been modified since they were copied from OpenCores into orpsocv2?

>> Like I mentioned earlier, I'd like to see this thing disappear altogether
>> and be replaced with gpio-generic.
>
> That needs device-tree support and published bindings first. IIRC, you
> had some preliminary code?

I thought I did, but I was mistaken.  I don't have anything for 
gpio-generic.

/Jonas

  parent reply	other threads:[~2013-11-15 10:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-09 20:37 [PATCH] openrisc: Add DTS and defconfig for DE0-Nano Geert Uytterhoeven
2013-11-10  5:51 ` Stefan Kristiansson
2013-11-10  8:18   ` Geert Uytterhoeven
2013-11-15  9:52   ` Jonas Bonn
2013-11-15 10:04     ` Andrew Back
2013-11-15 10:10       ` Geert Uytterhoeven
2013-11-15 10:19         ` Andrew Back
2013-11-15  9:50 ` Jonas Bonn
2013-11-15 10:22   ` Geert Uytterhoeven
2013-11-15 10:47     ` Geert Uytterhoeven
2013-11-15 10:57     ` Jonas Bonn [this message]
2013-11-15 11:39       ` Olof Kindgren
2013-11-15 11:57         ` Geert Uytterhoeven
2013-11-15 12:12         ` Jonas Bonn
     [not found]           ` <52860FC1.6050500-A9uVI2HLR7kOP4wsBPIw7w@public.gmane.org>
2013-11-15 15:16             ` [ORLinux] " Mark Rutland
     [not found]   ` <5285EE5A.1070202-A9uVI2HLR7kOP4wsBPIw7w@public.gmane.org>
2013-11-15 15:07     ` Mark Rutland
2013-11-16  8:45   ` Stefan Kristiansson
2013-11-16 11:01     ` Olof Kindgren
2013-11-17  8:44       ` [ORLinux] " Jonas Bonn
2013-11-17 13:46         ` Stefan Kristiansson
     [not found] ` <1384029451-16555-1-git-send-email-geert-Td1EMuHUCqxL1ZNQvxDV9g@public.gmane.org>
2013-11-20 20:45   ` Rob Herring

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=5285FE1D.3020800@southpole.se \
    --to=jonas@southpole.se \
    --cc=contact@kevinmehall.net \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@lists.openrisc.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).