Juan Jose Pablos a écrit :
> Pierre Bourgin escribió:
>> Hello list,
>>
>> Please find attached an updated version of the Windows drivers scan
>> system
>> for the Unattended project and some related informations about it.
>>
> Hi Pierre,
> I have a couple of questions about this stuff:
>
> is mandatory to enable sound on the Linux kernel for this to work?
If the sound support is not present in the kernel, the scanner will
still work, but it won't be able to detect HDAUDIO device (eg sound card).
This kind of hardware is a PCI device, but with a virtual high
definition audio bus, and windows drivers refer to it as HDAUDIO device,
not as PCI device ... so without HDAUDIO kernel support, no match with
Windows drivers.
I took a look on how to parse HDAUDIO buses without the need of linux
sound support, but it seems rather complicated (ALSA layer code), at
least too much for me ;-)
I believe that the cost of sound support is about +1.3MB in stage2/
content (uncompressed) (based on kernel 2.6.29); configuration has to be
done like this:
#added support of HDAUDIO via the alsa (kernel) layer (/proc/asound/...).
+- Device Drivers
+- <M> Sound Card Support
+- <M> Advanced Linux Sound Architecture
+- < > Sequencer support
+- < > OSS Mixer API
+- < > OSS PCM (digital audio) API
+- [ ] Dynamic device file minor numbers
+- [ ] Support old ALSA API
+- [ ] Verbose procfs contents
+- [ ] Verbose printk
+- [ ] Debug
+- [ ] Generic sound devices --->
+- [ ] USB sound devices --->
+- [ ] PCMCIA sound devices --->
+- < > ALSA for SoC audio support --->
+- [*] PCI sound devices --->
+- [] Support old ALSA API
+- [] Generic sound device
+- [M] PCI sound devices
+- (no driver selected here)
+- <M> Intel HD Audio
+- [ ] Build hwdep interface for HD-audio driver
(NEW)
+- [ ] Support digital beep via input layer (NEW)
+- [*] Build Realtek HD-audio codec support (NEW)
+- [*] Build Analog Device HD-audio codec support
(NEW)
+- [*] Build IDT/Sigmatel HD-audio codec support
(NEW)
+- [*] Build VIA HD-audio codec support (NEW)
+- [*] Build ATI HDMI HD-audio codec support (NEW)
+- [*] Build NVIDIA HDMI HD-audio codec support (NEW)
+- [*] Build INTEL HDMI HD-audio codec support (NEW)
+- [*] Build Conexant HD-audio codec support (NEW)
+- [*] Build C-Media HD-audio codec support (NEW)
+- [*] Build Silicon Labs 3054 HD-modem codec
support (NEW)
+- [*] Enable generic HD-audio codec parser (NEW)
+- [ ] Aggressive power-saving on HD-audio (NEW)
> can we use <unattended>/install/drivers instead of
> <unattended>/install/site/win_drivers/ ?
yes, as you prefer. IMHO we should use
<unattended>/install/win_drivers/
or <unattended>/install/drivers_win/
in order to let people better distinguish between linux/unattended stuff
and Windows materials ?
> Most drivers are ok to be used on win2000/winxp so we can easily put
> then on the same directory,
yes, this is the same driver model between 2000 and XP and 2003 if I
remember well.
> but what do you think about win7 and vista?
Some hints about drivers across windows flavors:
http://en.wikipedia.org/wiki/Windows_Driver_Model
indicates that Vista has a new driver model (shared with windows 7),
that is not the same than 2000/XP.
... and vista can support 2000/XP drivers...
So I don't know what people want:
1- keep a separate "database" of drivers: divided between XP and Vista
2- have a unified "database" of drivers (that is currently the model of
DriverPacks.net for instance).
Anyway, we can provides the root folder of drivers as configuration
option from command-line and site/config.pl via variable
$u->{'_temp'}->{'scan_windrivers_path'} in my example.
.. so we could also calculate a default value depending on the OS flavor
to install ?
and let people decide how they want to organize their windows drivers ?
Pierre
--
ARTERIS http://www.arteris.com
The Network-on-Chip Company
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
unattended-devel mailing list
unattended-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-devel
