On 12/2/2010 8:17 AM, Carsten Munk wrote:
2010/12/2 Arjan van de Ven<[email protected]>:
On 12/2/2010 4:32 AM, Carsten Munk wrote:
If there's suggestions how we handle global detection of what device
we run and configure accordingily, especially inside PulseAudio
configuration. I'd like to know this as well - I don't think we can
rely on autodetect for something as complex as audio configuration
when modems etc are involved.
it's very simple actually
you make pulseaudio try
/etc/pulse/foo.conf.<machinename>
before it tries
/etc/pulse/foo.conf
<machinename> on x86 comes from sysfs:
/sys/devices/virtual/dmi/id/board_name
on ARM apparently it may come from cpuinfo or something (but that's a
detail, if there is no board name you can do architecture name)
with that we can parallel ship a series of config files, and the right one
gets picked at runtime automatically.
but that also means that we can use the same image on multiple devices...
something rather important on x86
Sounds like a good direction. Maybe we should provide a simple package
wih '/usr/bin/meego-machinename' which outputs a proper machine name
in an arch-indep manner? (I guess we shouldn't encourage people to
parse /proc/cpuinfo or rely on /sys/devices/virtual/dmi/id/board_name
existence.. #ifdef __arm__ or x86 is so ugly :)
That, or a machine name being put in /etc/meego-machinename at startup
or something to avoid launching a process each time.
I like the /etc/meego-machinename thing or even just /etc/machinename
we can do the x86 side no big deal in a short time...
(heck it could just be a symlink to the sysfs file there)
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
