kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: luca@lucaceresoli.net (Luca Ceresoli)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Looking for ARM SoC porting guidelines
Date: Sun, 01 Feb 2015 10:15:12 +0100	[thread overview]
Message-ID: <54CDEEA0.3090507@lucaceresoli.net> (raw)
In-Reply-To: <CAEOSq-Ob0EkZhKGkYOwO5UQVinM-gV862WxXLh+D92=uzX8MbQ@mail.gmail.com>

Dear Mike,

Mike Thompson wrote:
[...]
> I'm still waiting for my N32926 hardware to arrive to begin a port for
> it.  Given the work I've done with the N32905 and the similarity between
> the two chips at the basic level, I don't anticipate it taking more than
> a few days to get it going.  I'll post back here when I have something
> to try.  At a minimum it would include the clock framework, clock
> source, interrupt driver, UART driver and other basic stuff.
>
>     Oh, and... any plans for supporting the H.264 decoder on the N32926?
>
> Well, for now I'm working on the basics and the first tier of drivers to
> the system so it can boot from NOR/NAND flash, SD cards and have basic
> USB connectivity. I already have these items on the N32905.  I don't
> have any specific plans beyond that for the N32926, but we'll see. My
> specific interest is in the lower-end N32905 because of the opportunity
> for the chip in the toy markets and a $3 Linux capable single chip
> system is really cool :-).

Any news on your project? There seem to be no more commits since several
weeks on your github repository...

-- 
Luca

  reply	other threads:[~2015-02-01  9:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13  5:45 Looking for ARM SoC porting guidelines Mike Thompson
2014-11-13  8:40 ` Maxime Ripard
2014-11-13 18:41   ` Mike Thompson
2014-11-14  9:03     ` Maxime Ripard
2014-11-14 17:10     ` Luca Ceresoli
2014-11-14 21:00       ` Mike Thompson
2015-02-01  9:15         ` Luca Ceresoli [this message]
2015-02-02 19:26           ` Mike Thompson

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=54CDEEA0.3090507@lucaceresoli.net \
    --to=luca@lucaceresoli.net \
    --cc=kernelnewbies@lists.kernelnewbies.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).