linux-kernel - Re: [Arm-netbook] [advice sought] EOMA68 kernel support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1331383208.29393.18.camel@home.hno.se>
Date:	Sat, 10 Mar 2012 13:40:08 +0100
From:	Henrik Nordström <henrik@...riknordstrom.net>
To:	Linux on small ARM machines <arm-netbook@...ts.phcomp.co.uk>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [Arm-netbook] [advice sought] EOMA68 kernel support

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/