2011/1/12 Arjan van de Ven <[email protected]>: > On 1/12/2011 9:54 AM, Carsten Munk wrote: >> >> 2011/1/12 Chris Ferron<[email protected]>: >>> >>> Hi, >>> Please remove package policy-settings-basic-ncdk from project >>> Trunk:Testing >>> >>> Reason: This package is not appropriately named and might not be >>> correct. >>> having a policy settings for mfld may be ok, but not for various version >>> of mfld. (ie iCDK vs nCDK). >>> At very least the name is wrong. >> >> Out of technical curiousity, how do you tell iCDK and nCDK apart on >> run-time? > > DMI information > > kernel exposes that via sysfs in /sys/devices/virtual/dmi/id/product_name > and/or board_name > > (this is the standard IA way of enumerating what board you're on)
OK, which does return INVALID on my laptop for instance. So, I'm personally tired of us not having a good auto-detection way and I think we should get the idea about /etc/boardname as we discussed at length while ago[1] implemented ASAP. Can we somehow get this work started and into MeeGo with deadline next week so we have an uniform way of determining a device name for components to use and use different behaviour/configurations/etc for different devices within MeeGo? I'll commit for ARM side to get it done this week. Who'll commit from IA side to implement it? Auke proposed a 'boardname' gitorious repo and I didn't hear anything since, so we can have that as starting point. [1] http://lists.meego.com/pipermail/meego-packaging/2010-December/246089.html /Carsten _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
