On Thu, Sep 18, 2014 at 05:35:42PM -0700, nitin.a.kam...@intel.com wrote: > From: Nitin A Kamble <nitin.a.kam...@intel.com> > > Add machine configuration for the NUC platform in the intel-corei7-64 BSP > image. > > Signed-off-by: Nitin A Kamble <nitin.a.kam...@intel.com> > --- > .../machinesetuptool/intel-corei7-64/nuc-alsa.conf | 24 ++ > .../intel-corei7-64/nuc-alsa.state | 309 > +++++++++++++++++++++ > .../nuc-bootscript-hdmi_port_audio.sh | 19 ++
So on alsa and HDMI, I've discussed this with some alsa devs and I got the impression this sort of machine specific configuration should not be necessary. I'd suggest connecting with Mengdong Lin and discussing options for a more generic means to enable alsa and HDMI. > .../intel-corei7-64/nuc-formfactor.machconfig | 3 + > .../intel-corei7-64/nuc-network.interfaces | 31 +++ > .../machinesetuptool/intel-corei7-64/nuc.vars | 14 + > .../machinesetuptool/machinesetuptool_git.bbappend | 18 ++ > 7 files changed, 418 insertions(+) > create mode 100644 > common/recipes-bsp/machinesetuptool/machinesetuptool/intel-corei7-64/nuc-alsa.conf > create mode 100644 > common/recipes-bsp/machinesetuptool/machinesetuptool/intel-corei7-64/nuc-alsa.state > create mode 100755 > common/recipes-bsp/machinesetuptool/machinesetuptool/intel-corei7-64/nuc-bootscript-hdmi_port_audio.sh > create mode 100644 > common/recipes-bsp/machinesetuptool/machinesetuptool/intel-corei7-64/nuc-formfactor.machconfig > create mode 100644 > common/recipes-bsp/machinesetuptool/machinesetuptool/intel-corei7-64/nuc-network.interfaces > create mode 100644 > common/recipes-bsp/machinesetuptool/machinesetuptool/intel-corei7-64/nuc.vars > create mode 100644 > common/recipes-bsp/machinesetuptool/machinesetuptool_git.bbappend > ... > diff --git > a/common/recipes-bsp/machinesetuptool/machinesetuptool/intel-corei7-64/nuc-network.interfaces > > b/common/recipes-bsp/machinesetuptool/machinesetuptool/intel-corei7-64/nuc-network.interfaces > new file mode 100644 > index 0000000..0acf4cf > --- /dev/null > +++ > b/common/recipes-bsp/machinesetuptool/machinesetuptool/intel-corei7-64/nuc-network.interfaces > @@ -0,0 +1,31 @@ > +# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) > + > +# The loopback interface > +auto lo > +iface lo inet loopback > + > +# Wireless interfaces > +iface wlan0 inet dhcp > + wireless_mode managed > + wireless_essid any > + wpa-driver wext > + wpa-conf /etc/wpa_supplicant.conf > + > +iface atml0 inet dhcp > + > +# Wired or wireless interfaces > +auto eth0 > +iface eth0 inet dhcp > +iface eth1 inet dhcp Does the nuc really have all these interfaces? Seems like a lot of generic bits for a machine-specific config... > + > +# Ethernet/RNDIS gadget (g_ether) > +# ... or on host side, usbnet and random hwaddr > +iface usb0 inet static > + address 192.168.7.2 > + netmask 255.255.255.0 > + network 192.168.7.0 > + gateway 192.168.7.1 > + > +# Bluetooth networking > +iface bnep0 inet dhcp > + > diff --git > a/common/recipes-bsp/machinesetuptool/machinesetuptool/intel-corei7-64/nuc.vars > > b/common/recipes-bsp/machinesetuptool/machinesetuptool/intel-corei7-64/nuc.vars > new file mode 100644 > index 0000000..c6f373f > --- /dev/null > +++ > b/common/recipes-bsp/machinesetuptool/machinesetuptool/intel-corei7-64/nuc.vars > @@ -0,0 +1,14 @@ > +FORMFACTOR_FILE="nuc-formfactor.machconfig" > +ALSA_CONFIG_FILE="nuc-alsa.conf" > +ALSA_STATE_FILE="nuc-alsa.state" > +XORG_CONFIG_FILE="" > +NETWORK_INTERFACES_FILE="nuc-network.interfaces" > +AUTOLOAD_KERNEL_MODULES="uio iwlwifi" Don't we already do this for the intel-common kernel? -- Darren Hart Intel Open Source Technology Center -- _______________________________________________ meta-intel mailing list meta-intel@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-intel
