1 |
On Mon, 2004-10-11 at 13:17, Greg KH wrote: |
2 |
> On Mon, Oct 11, 2004 at 11:24:14AM -0400, Ned Ludd wrote: |
3 |
> > On Mon, 2004-10-11 at 07:35, Chris Gianelloni wrote: |
4 |
> > > I just wanted to remind everyone that the deadline for something making |
5 |
> > > it into 2004.3 is Friday, since we will be running our snapshot on the |
6 |
> > > 16th. This means any package that we want on the LiveCD needs to be |
7 |
> > > marked *STABLE* for any arch that wants the package. |
8 |
> > > |
9 |
> > |
10 |
> > > latexer: Any chance we'll have madwifi-* ready? |
11 |
> > |
12 |
> > probably not. madwifi is a work in progress and results very depending |
13 |
> > on the kernel version. >=2.6.8 is a no go. |
14 |
> |
15 |
> Is this a problem with the kernel, or in the madwifi package? |
16 |
|
17 |
Both but lets say the madwifi needs work for >2.6.8 and then only on |
18 |
some >2.6.8. latexer gave me some ideas what needed to be done there for |
19 |
>2.6.8 and I sent him a partial ebuild patch. We know that the -mm |
20 |
series is not an option with some read-only assignment to a struct which |
21 |
never happenes with other series. Which ever patch that causes that from |
22 |
the -mm seems to have stunk into a kernel or two other. I don't know |
23 |
which patch or the root cause of what's up with that struct. (method and |
24 |
a few others might have some insight) |
25 |
|
26 |
But overall madwifi-driver is just not a stable project yet and probably |
27 |
should not be put in stable. |
28 |
Granted it would make life easier on a lot of us (mine atleast) if it |
29 |
was in stable but we would have to understand that it's still an |
30 |
unstable product. |
31 |
|
32 |
> |
33 |
> thanks, |
34 |
> |
35 |
> greg k-h |
36 |
-- |
37 |
Ned Ludd <solar@g.o> |
38 |
Gentoo (hardened,security,infrastructure,embedded,toolchain) Developer |