mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Henrik Nordström" <henrik@henriknordstrom.net>
To: Linux on small ARM machines <arm-netbook@lists.phcomp.co.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Arm-netbook] [advice sought] EOMA68 kernel support
Date: Sat, 10 Mar 2012 13:40:08 +0100	[thread overview]
Message-ID: <1331383208.29393.18.camel@home.hno.se> (raw)
In-Reply-To: <CAPweEDysGTCNp+6SCCpzBorwn5ZczNNgV0E+mBLe0FwfE=3Wqw@mail.gmail.com>

lör 2012-03-10 klockan 06:45 +0000 skrev lkcl luke:

>  ... so, real simple very basic, concrete and necessary question:
> where the hell in the linux kernel tree should support for eoma68 be
> added??

Good question.

There is two parts of eoma68 relevant to this

First, there is the capabilitities of the CPU card itself.

Second, there is the I/O board it gets connected to.

These two parts need to be matched, resulting in a device tree or
similar for the actual system in it's current form, and is something
that may even change dynamically at suspend/resume. The I/O board may
cause different I/O profiles to be selected bu the CPU card. A
theoretical example would be one configuraiton having LCD, the other
doing 10 UARTs on the same lines. This requires the CPU card to adopt in
which hardware devices it activates, something ARM SoCs is quite good at
and A10 in particular.

We do not know yet which I/O profiles of EOMA will be available or used
for. The current profile is based on the expected initial target
systems.

The EOMA connector in itself is a kind of I/O bus.

Regards
Henrik


  reply	other threads:[~2012-03-10 13:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09 22:41 lkcl luke
2012-03-10  6:45 ` lkcl luke
2012-03-10 12:40   ` Henrik Nordström [this message]
2012-03-10 13:00   ` Alan Cox
2012-03-10 13:25     ` lkcl luke
2012-03-10 19:51       ` Alan Cox
2012-03-10 20:20         ` lkcl luke

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=1331383208.29393.18.camel@home.hno.se \
    --to=henrik@henriknordstrom.net \
    --cc=arm-netbook@lists.phcomp.co.uk \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®