Bugzilla Bug 44103

I'd like to see an ebuild for the acx100 driver. It works fine with 2.6 and
2.4. I had two solutions in mind:
1.) add as seperate driver
2.) add as kernel-patch

since in 2.6 you have to compile the driver in kernel path, the second idea is
what i like most. but currently this is not supported via "make menuconfig",
but i will ask the developers for adding this support. take a look at the URL i
added.

i'd like to make an ebuild by myself, but i really lack knowledge in
kernel-ebuilds and currently have no time to learn it.

Reproducible: Always
Steps to Reproduce:

To easy the pain :)

http://luca.pca.it/projects/acx100/

This site hosts a kernel patch (i haven't had the time to test it, will give feedback when i'm done testing)

The patch works with some issues:
- it only works against /usr/src/linux-2.6.3-acx100
- patching Makefile failes! (added support by hand)
- Kconfig changes are made three times, which causes that there are three entries in "make menuconfig"

i found out that the current cvs-version supports compilation outside of the
kernel tree. this would make an ebuild much simpler. i will give it a try later
this day.

Created an attachment (id=28003) [details]
net-wireless/acx100-0.2.0_pre7.ebuild

NON-WORKING ebuild for the acx100 driver. It crashes during a sandbox violation
and i can't figure out why :( Maybe someone with knowledge might take a look at
it.

Created an attachment (id=30171) [details]
net-wireless/acx100-0.2.0_pre8.ebuild

NON-WORKING ebuild for new version. it still sandbox-violates. if someone could
help me rewriting the "make install" i guess it would work.

I've been looking into this, and may I suggest that the user installs the
firmware himself, as there are so many different versions that actually work
(eg my dwl-560+ uses a differnet firmware to the 520+ afaik), also there is
currently no way to get around the sandbox violations, you've just got to set
FEATURES="-sandbox". 

Adding lots of instructions on the end on where to get the various firmwares
and where to put which files should be ok. I'll post an updated ebuild tomorrow
at some point

Well, I'm not sure that anyone is still working on this thing however I have
come up with a better way to do the pre version / fix deal.  It goes something
like this.

Filename:  acx100-0.2.0_pre8-r14.ebuild

then have this code in the ebuild itself that will set all the version stuff
for you.

VER=${PV/"_"/""}
REV=${PR/"r"/"_plus_fixes_"}
ACX_VER=${PN}-${VER}${REV}


SRC_URI="http://rhlx01.fht-esslingen.de/~andi/acx100/${ACX_VER}.tar.bz2"

This is a hack so it might not conform to portage standards, however not sure
what else we could do since the filename from acx seems a little strange.

Anyone made any progress with getting this thing to compile?

Also I agree that downloading would be best I suppose.  However, I think one
could get quite complex and try to pull the information from /proc/pci to see
which card the user has???

I'm working on an ebuild, if I have any luck I'll post it here.

I tried to fix my ebuild to get this running, but for me it's impossible, since
it  calls functions ("make", i think) in the /usr/src/linux directory. My idea
was:

./Configure || die "configure failed"
sed -i -e "s:=\/:=\$\{D\}\/:g" config.mk ||

I tried to fix my ebuild to get this running, but for me it's impossible, since
it  calls functions ("make", i think) in the /usr/src/linux directory. My idea
was:

./Configure || die "configure failed"
sed -i -e "s:=\/:=\$\{D\}\/:g" config.mk ||¢die "sed failed"
dodir `grep KERNEL_BUILD config.mk | cut -c 18-` || die "dodir failed"
dodir `grep KERNEL_OUTPUT config.mk | cut -c 19-` || die "dodir failed"
dosym ${ROOT}${KERNEL_DIR} ${D}/`grep KERNEL_BUILD config.mk | cut -c 18-` ||
die "symlinking failed"
make || die "make failed"

The symlink wouldn't work for me, but maybe someone else can use this idea.

Next to that: Christopher Fords idea look very good to me!!

The ACX100 developpers do not send the new versions to Sourceforge anymore. You
can find the latest builds at http://lisas.de/~andi/acx100/.

Additional hint: According to bug #32737 someone got acx100 building with an
ebuild. I'm not sure how he did this, I wasn't able to do so. Maybe someone
else could try it.

I failed with a missing firmware.eclass. But since there is no need for that
(the user should get the firmware himself), it might work, but I have a huge
lack of time so I cannot do it :(

Created an attachment (id=45699) [details]
net-wireless/acx100-0.2.0_pre8

Ladies and gentleman ... i proudly present:

The WORKING acx100 ebuild :D

forgot to say: tested with 2.6 kernel, only. someone should check 2.4 since I'm
quite sure the install routine will fail.

Created an attachment (id=49398) [details]
acx100-0.2.0_pre8.ebuild

please test and comment if this works for you.

in portage, thanks