On Saturday 26 May 2007 19:24:33 Uwe Bugla wrote: > Am Samstag, 26. Mai 2007 19:18 schrieben Sie: > > On Saturday 26 May 2007 19:04:04 Uwe Bugla wrote: > > > Yes, sure! But the help text is very unlucky and humble, and it is not > > > clear enough in the sense of being distinctive enough, just clear and > > > comprehensive. > > > > Why don't you simply submit a patch to change the helptext then? > > I'm not sure why you refuse to DO anything about the "mess", but > > instead keep poking me that I am responsible somehow to fix it up > > for you... > > I need exception examples for doing so. What are the exception examples? > > Apart from that you have don nothing except than guessing around. Admit it. You don't know how debugging is done in the real world. Debugging _IS_ guessing around. > Now here comes the LAST proof that your code is buggy: > > A. It's not mm-implementation > B. It's not user behaviour or fault > C. It's not an ACPI issue > > BUT ONE AND ONLY: > > D. It's your code that is buggy, without any doubt! Blahblah. Did you even read the mail I CCed to you? It "proves" (to use your wording) the exact opposite. > OK, went Andrew's path: patched 2.6.22-rc3 with wireless tree: > > Result: The NIC driver b44 and ssb are loaded correctly, but refuse to work > (no network communication possible). Ok, please take git and get my development tree and try with that: git clone http://bu3sch.de/git/wireless-dev.git It's based on 2.6.22-rc1 and it works fine for me. > dmesg: > ... Ok, config and dmesg looks OK to me, now. -- Greetings Michael. - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
