> Actually i disable building macbook pro support because it access the pci bus > directly and starts poking into /dev/mem. Which imho is scary and wrong. This > work should be done by a kernel driver, not by some usespace tool poking in > pci memory space. > > Sjoerd
Well... *something* needs to be poking those values, whether it's running in kernel space or in user space. The strongest argument I can see against having such code in HAL is that it means that no other HAL-like framework can just build off the work without copy-pasting the code. I can see why your inclinations would be against the way the macbook{,pro} addons do things, but with no evidence of any place where things go wrong (AFAIK?), and with the realization that if it were a kernel-space driver it would be doing exactly the same things, should those of us running macbooks just accept that we will need to rebuild HAL on every update to get proper functionality? My first day using Debian, I noticed this as a regression over the functionality other distros have provided. ~Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]