linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mostawesomedude@gmail.com (Corbin Simpson)
To: linux-arm-kernel@lists.infradead.org
Subject: How to allocate a new machine type?
Date: Tue, 4 May 2010 15:17:48 -0700	[thread overview]
Message-ID: <i2ge7bd23c31005041517k33229b87g7f974d6642995706@mail.gmail.com> (raw)
In-Reply-To: <20100504215328.GK30601@n2100.arm.linux.org.uk>

On Tue, May 4, 2010 at 2:53 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Tue, May 04, 2010 at 02:32:15PM -0700, Corbin Simpson wrote:
>> So, I noticed that there's a Pollux entry, POLLUX_WIZ (1950), in the
>> mach-types list already. Does anybody know if that covers all Pollux
>> devices, or just the Wiz? Also, what do I have to do to allocate a new
>> type?
>
> It's for "GamePark Holdings GP2X Wiz". ?So it seems its only for the Wiz.
>
> ? Machine name: ? ? GamePark Holdings GP2X Wiz
> ? Web site: ? ? ? ? http://www.gp2xwiz.com/
> ? Description: ? ? ?The GP2X Wiz is a handheld video game machine using the
> ? ? ? ? ? ? ? ? ? ? MagicEyes Pollux SoC.
>
> For information on machines, including registering new ones, etc, see
> the bottom of Documentation/arm/README in the kernel tree.

Russell,

Thank you for the quick reply. Type 2028 appears to be the Didj,
allocated by one of the OpenWiz guys. I will use that.

While the merge window is still open, is it kosher to send patches to
this list for upstream? I have a few patches that don't rely on the
arch-lf1000/arch-pollux code that I'd like to unload. I know that I'm
new to this part of the kernel, but I think I'm learning quickly.

~ C.

-- 
When the facts change, I change my mind. What do you do, sir? ~ Keynes

Corbin Simpson
<MostAwesomeDude@gmail.com>

  reply	other threads:[~2010-05-04 22:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04 21:32 How to allocate a new machine type? Corbin Simpson
2010-05-04 21:53 ` Russell King - ARM Linux
2010-05-04 22:17   ` Corbin Simpson [this message]
2010-05-04 23:45     ` Marek Vasut

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=i2ge7bd23c31005041517k33229b87g7f974d6642995706@mail.gmail.com \
    --to=mostawesomedude@gmail.com \
    --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).