First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 138644
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Mobile Herd <mobile@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Sebastian <sebastian_ml@gmx.net>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
rt61-1.1.0_beta1.ebuild v1.1.0-b1 ebuild text/plain Sebastian 2006-06-30 17:30 0000 1.19 KB Details
rt61-9999.ebuild CVS ebuild text/plain Sebastian 2006-06-30 17:30 0000 1.44 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 138644 depends on: Show dependency tree
Show dependency graph
Bug 138644 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-06-30 17:29 0000 
Hi all!

We don't have it yet, allthough we have most of the others (rt2400, rt2500,
rt2x00). I put together two ebuilds; one for v1.1.0-b1 and one for the rt61 CVS
(kudos to the existing rt2x00 CVS ebuild).

Three things:
1. I used MODULESD_RT61_ALIASES=('ra? rt61'); maybe "ra0" is the way to go?
2. The driver source includes 3 firmware files and the ebuilds puts them in the
proper place (no hotplug firmware loading yet). Is this legal from Gentoo's
point of view?
3. Thanks :)

Sebastian

------- Comment #1 From Sebastian 2006-06-30 17:30:20 0000 ------- 
Created an attachment (id=90579) [edit]
v1.1.0-b1 ebuild

------- Comment #2 From Sebastian 2006-06-30 17:30:43 0000 ------- 
Created an attachment (id=90580) [edit]
CVS ebuild

------- Comment #3 From Stefan Schweizer 2006-07-01 05:14:37 0000 ------- 
thanks I committed the beta1 ebuild. The cvs ebuild is something I cannot
really maintain in the tree without having the hardware. When there are
important changes, please request a new release from upstream or make a
tarball.
First Last Prev Next    No search results available      Search page      Enter new bug