Assuming problem shows 2.6/hme but not 2.4/hme then it is
a problem in 2.6 hme driver (?) or how the 2.6 hme driver
interacts with other supporting 2.6 kernel code.



The problem appears to be related to 2.6 only (tested using 2.4.30 on an SMP Ultra 2 and it worked no problem). Not exactly where in 2.6 this started but we have one report of 2.6.5 working as expected (so presumably sometime after that).



In the "silly question" category, does anyone keep a CVS
tree of the kernel that I could log/diff to track the changes to
this file?  I know that git is now being used, but does the
current git tree track all changes to the *hme* files?

Thanks
--
[email protected] mailing list



Reply via email to