Hi, Wenceslao González-Viñas wrote:
> From your last post concerning this bug, I did not get what should > be the procedure from now on. I would suggest looking at the driver code, adding printk calls to find out what it reads from the NVRAM (to confirm Ben's hypothesis), and if it is blank, coming up with a better behavior and proposing it in the form of a rough patch to the linux-wireless list. If you are not a programmer or lack time, that's okay; in that case the best thing to do is just to be ready to test patches if someone else embarks on that same adventure. Hope that helps, and sorry I don't have anything more helpful to provide. Regards, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
