From: Howard Young <howardiyoung@ho...> - 2006-01-16 19:11:52
reading some of your recent posts i hope to help by suggesting:
1) stop new development for a short while, (to get more time for this:)
2) the drivers work well for most do they not? (i can browse the
3) security is a second issue for the majority of users (I am thinking of
the people who just bought wireless and broadband packages and don't know
wep from wap).
4) work on the error reporting and packaging of the driver (less stupid
errors more real debugging, while errors are hidden from the user and then a
script can be run by the user at some point to post all the errors and
needed information in one go... in my opinion this would be a good idea
where non developer users are involved)
5) get the user enhanced drivers available to stable and mainstream linuxes
in package formats, even if that means self compiling packages. I am not
suggesting the MS Update style scenario, i think of just a single driver
that works as best it presently is able and providing that as the 'to be
used' and 'easily' driver for general use but non technical people.
6) Once this is done and the packages are available move the code into the
main area where it should be (assuming that server is now fast enough to be
7) sift through tidying with consideration for 'the other driver'
8) start adding updates to the main tree so that the model is a bit better
(going by what was written in the state of union email).
Lastly if the packaging works well and the tidying then some frame work to
make driver use more popular but at the same time less work (remember less
install problems and so on) then you could continue for future releases.
This is all a bit silly sounding to me but i hoped that a user type
perspective might be useful.
your drivers work but need to be more accessible and always the correct
if i knew how to driver compile to a .deb or for debsrc that would install
on any debian then i would but at the moment i have not had time to learn
this. to be able to type apt-src build acx-drivers would be great and if it
fed back driver debug info to you then that would be even better.
Howard Young wrote:
> if i knew how to driver compile to a .deb or for debsrc that would
> install on any debian then i would but at the moment i have not had time
> to learn this. to be able to type apt-src build acx-drivers would be
> great and if it fed back driver debug info to you then that would be
> even better.
The driver is already in Debian, you could found it as acx100-source,
you could try it, the last version in Debian is now, 20051202, i supose
I will try a new version in a few days. If you want to say any comment
on it, please mail me.
e-mail: Miguel Gea Milvaques <debian(@nospam)miguelgea.com
GnuPG key: 0x580808C4
Key fingerprint = 85A0 06FD 9A6C 4701 27C2 5536 3533 50CA 5808 08C4