From: kentborg@borg.org (Kent Borg)
To: linux-arm-kernel@lists.infradead.org
Subject: mach header files
Date: Fri, 04 Apr 2014 15:01:01 -0400 [thread overview]
Message-ID: <533F016D.9050700@borg.org> (raw)
In-Reply-To: <5208350.A2oo5ltmuY@wuerfel>
On 04/04/2014 02:49 PM, Arnd Bergmann wrote:
> The trouble with examples here is that the good ones are those without
> any code, which is harder to copy than the bad ones ;-)
Indeed.
> mach-sunxi is a rather good example, [...] An ideal example is
> mach-moxart, which has zero code.
Cool.
> Can you say what platform you are working on?
Doesn't exist yet, as I said I am running an emulation, trying to get
Linux up, but also part of verifying design. Pretty sure no marketing
announcements have been made; I don't think I can blab before the suits do.
-kb
next prev parent reply other threads:[~2014-04-04 19:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 8:19 mach header files Phil Edworthy
2014-04-04 10:29 ` Grant Likely
2014-04-04 12:16 ` Phil Edworthy
2014-04-04 12:22 ` Grant Likely
2014-04-04 13:14 ` Phil Edworthy
2014-04-04 13:20 ` Thomas Petazzoni
2014-04-08 14:00 ` Laurent Pinchart
2014-04-04 13:44 ` Grant Likely
2014-04-04 13:24 ` Arnd Bergmann
2014-04-04 13:32 ` Barry Song
2014-04-04 15:27 ` Arnd Bergmann
2014-04-04 13:52 ` Phil Edworthy
2014-04-04 15:30 ` Arnd Bergmann
2014-04-04 15:42 ` Phil Edworthy
2014-04-04 15:50 ` Arnd Bergmann
2014-04-04 16:02 ` Phil Edworthy
2014-04-04 16:22 ` Russell King - ARM Linux
2014-04-04 16:38 ` Phil Edworthy
2014-04-04 18:01 ` Kent Borg
2014-04-04 18:49 ` Arnd Bergmann
2014-04-04 19:01 ` Kent Borg [this message]
2014-04-04 19:19 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2014-04-02 15:11 Phil Edworthy
2014-04-02 15:16 ` Arnd Bergmann
2014-04-03 7:48 ` Phil Edworthy
2014-04-02 15:20 ` Ben Dooks
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=533F016D.9050700@borg.org \
--to=kentborg@borg.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).