| 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
| ||
|
Message-ID: <1312986047.2989.47.camel@i7.infradead.org> Date: Wed, 10 Aug 2011 15:20:46 +0100 From: David Woodhouse <dwmw2@...radead.org> To: Vivien Didelot <vivien.didelot@...oirfairelinux.com> Cc: Corentin Chary <corentin.chary@...il.com>, Ike Panhc <ike.pan@...onical.com>, linux-kernel@...r.kernel.org, mjg@...hat.com, platform-driver-x86@...r.kernel.org Subject: Re: [RESEND][PATCH 0/5] Support for the TS-5500 board On Wed, 2011-08-10 at 10:06 -0400, Vivien Didelot wrote: > > And btw, I'm not sure we really want to put all these drivers in > > arch/x86/platform/ts5500/ a re-create the arm driver mess. > > drivers/leds/, drivers/gpio/ and drivers/mtd/ are probably a best > > choice. > > In fact, this set of patches is a rewrite of the first RFC set, where > we discussed that arch/x86/platform/ could be a good place, as the > TS-5500 is a specific platform with its platform devices (the > corresponding thread is here: https://lkml.org/lkml/2011/5/3/60). Just expose these devices in the device-tree. You shouldn't *need* a new MTD device driver; physmap_of should be just fine. If your bootloader doesn't pass one, your platform-specific code should just register its own device-tree blob during early boot. And your device drivers should just match against the devices therein. -- dwmw2 -- 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/
Powered by blists - more mailing lists