linux-kernel - Re: [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: <CAPweEDysGTCNp+6SCCpzBorwn5ZczNNgV0E+mBLe0FwfE=3Wqw@mail.gmail.com>
Date:	Sat, 10 Mar 2012 06:45:15 +0000
From:	lkcl luke <luke.leighton@...il.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc:	Linux on small ARM machines <arm-netbook@...ts.phcomp.co.uk>
Subject: Re: [advice sought] EOMA68 kernel support

On Fri, Mar 9, 2012 at 10:41 PM, lkcl luke <luke.leighton@...il.com> wrote:

> the implications of that split, for the linux kernel source code, are
> a bit... scarey :)

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

 * driver support can't be added to drivers/ because although a device
with an EOMA68 CPU card *requires* drivers, it's not *actual* drivers
being added, it's driver *grouping* code that's required, and that
concept simply does... not... exist.

 * architecture support can't be added to arch/ because that contains
code for CPUs not code that is about helping to support multiple CPUs.
 eoma isn't a CPU.

 * adding a top-level directory "eoma" is a bit too "whoa" but i
really don't see any suitable subdirectories.

so.

very basic question.  where the hell should EOMA support source code go?

bearing in mind that the first CPU card is an Allwinner A10, the next
one is likely to be an AMD Fusion, the one after that could be from
icubecorp, the one after that a multi-core SMP xtensa, etc.

l.
--
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/