>> This is not a blob in the sense that it could be potentiallyAnd this makes it non-dangerous..how, exactly? Do you never send anything over your network interfaces or something? The firmware is perfectly positioned to meddle with and/or snoop on anything sent or received over that interface. Only if the DMA mapping is set up to allow it access to that RAM - or if your machine is so stupidly designed that a DMA bus master can access memory it hasn't specifically been set up with access to. While there are undoubtedly such systems, I would hope that nothing using a wpi would be quite that low-end. I do, however, know that it's not going to be used on *my* systems. (I won't use an ath either, because of the lack of source to the HAL.) /~\ The ASCII der Mouse \ / Ribbon Campaign X Against HTML mouse@rodents.montreal.qc.ca / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
| Eric Sandeen | Re: [RFC] Heads up on sys_fallocate() |
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 007/196] Chinese: add translation of stable_kernel_rules.txt |
| Andrew Morton | -mm merge plans for 2.6.23 |
git: | |
| David Miller | Re: [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
