| 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
| ||
|
Date: Wed, 10 Aug 2011 15:09:19 -0400 From: Vivien Didelot <vivien.didelot@...oirfairelinux.com> To: David Woodhouse <dwmw2@...radead.org> 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, 10 Aug 2011 15:20:46 +0100, David Woodhouse <dwmw2@...radead.org> wrote: > Just expose these devices in the device-tree. You shouldn't *need* a > new MTD device driver; physmap_of should be just fine. I didn't write a new MTD device driver, but just moved the already existing one to the ts5500 platform directory. The point is that my TS-5500 doesn't have this flash, so I couldn't try. The fifth patch from this set could just be ignored. > 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. I'm a bit confused with what should be done for the support for an embedded platform (X86-based) like this TS-5500. Is the actual code hierarchy OK? What is the impact of adding a device-tree to this code? Thanks, Vivien. -- 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