Mikhail Gusarov [EMAIL PROTECTED] wrote:
You ([EMAIL PROTECTED]) wrote:
H If you know more, please add your knowledge below.
[skip]
2.6.14-2 still enables the outdated ieee80211 :(
Fixing this is simply a matter of disabling CONFIG_IEEE80211. This
will allow to use ipw2200 (ipw2100
On Wed, Nov 30, 2005 at 06:51:44AM +, Horms wrote:
Mikhail Gusarov [EMAIL PROTECTED] wrote:
You ([EMAIL PROTECTED]) wrote:
H If you know more, please add your knowledge below.
[skip]
2.6.14-2 still enables the outdated ieee80211 :(
Fixing this is simply a matter of
On Wed, Nov 30, 2005 at 10:09:54AM +0100, Maximilian Attems wrote:
On Wed, Nov 30, 2005 at 06:51:44AM +, Horms wrote:
Mikhail Gusarov [EMAIL PROTECTED] wrote:
You ([EMAIL PROTECTED]) wrote:
H If you know more, please add your knowledge below.
[skip]
2.6.14-2
On Wed, Nov 30, 2005 at 06:22:17PM +0900, Horms wrote:
On Wed, Nov 30, 2005 at 10:09:54AM +0100, Maximilian Attems wrote:
On Wed, Nov 30, 2005 at 06:51:44AM +, Horms wrote:
Mikhail Gusarov [EMAIL PROTECTED] wrote:
You ([EMAIL PROTECTED]) wrote:
H If you know more,
On Wednesday 30 November 2005 11:44, Maximilian Attems wrote:
On Wed, Nov 30, 2005 at 06:22:17PM +0900, Horms wrote:
Ok, so I should just go ahead and put my patch into the 2.6.14 branch?
Or should we leave it as 2.6.15 probably isn't that far away... maybe
depends if d-i will base itself
On Wed, Nov 30, 2005 at 12:49:28PM +0100, Frans Pop wrote:
On Wednesday 30 November 2005 11:44, Maximilian Attems wrote:
On Wed, Nov 30, 2005 at 06:22:17PM +0900, Horms wrote:
Ok, so I should just go ahead and put my patch into the 2.6.14 branch?
Or should we leave it as 2.6.15 probably
On Wednesday 30 November 2005 16:06, Maximilian Attems wrote:
better ntfs support, up2date ipw2XXX, vfs support shared subtree,
fbcon console rotation + usual bunch of fixes and driver upgrades.
no acpi change.
Nothing that should give us problems I think. Thanks.
FB console rotation could be
On Wed, Nov 30, 2005 at 12:49:28PM +0100, Frans Pop wrote:
On Wednesday 30 November 2005 11:44, Maximilian Attems wrote:
On Wed, Nov 30, 2005 at 06:22:17PM +0900, Horms wrote:
Ok, so I should just go ahead and put my patch into the 2.6.14 branch?
Or should we leave it as 2.6.15 probably
On Wednesday 30 November 2005 21:04, Sven Luther wrote:
Are there major changes from .14 to .15? If not, we should be able to
change over to .15 relatively fast.
.15 will bring a non-negligible amount of change to powerpc, going from
ARCH=ppc|ppc64 to ARCH=powerpc, which may entail
On Wed, Nov 30, 2005 at 11:58:17PM +0100, Frans Pop wrote:
On Wednesday 30 November 2005 21:04, Sven Luther wrote:
Are there major changes from .14 to .15? If not, we should be able to
change over to .15 relatively fast.
.15 will bring a non-negligible amount of change to powerpc, going
On Thu, Dec 01, 2005 at 12:26:25AM +0100, Frans Pop wrote:
On Thursday 01 December 2005 00:09, Sven Luther wrote:
Yeah, but the change from ARCH=ppc | ARCH=ppc64, to a single re-unified
ARCH=powerpc kernel will not go without glitch, especially for the
lesser subarches (oldworld, prep, apus
In gmane.linux.debian.devel.kernel Maximilian Attems [EMAIL PROTECTED] wrote:
On Wed, Nov 30, 2005 at 12:49:28PM +0100, Frans Pop wrote:
On Wednesday 30 November 2005 11:44, Maximilian Attems wrote:
On Wed, Nov 30, 2005 at 06:22:17PM +0900, Horms wrote:
Ok, so I should just go ahead and put
You ([EMAIL PROTECTED]) wrote:
H If you know more, please add your knowledge below.
[skip]
2.6.14-2 still enables the outdated ieee80211 :(
Fixing this is simply a matter of disabling CONFIG_IEEE80211. This
will allow to use ipw2200 (ipw2100 also) drivers built using
module-assistant as
On Sat, Nov 05, 2005 at 12:21:00AM +, Christoph Hellwig wrote:
On Fri, Nov 04, 2005 at 12:29:20PM +0900, Horms wrote:
do I take that comment to mean that upstream can't update the
drivers but Debian can? And if so, do you recommend updating
Debian's kernel packages, or putting the
On Fri, Nov 04, 2005 at 01:51:24AM -0500, Joey Hess wrote:
Horms wrote:
I don't have a particular problem with disabling those drivers from the
build. But the d-i guys might. I've CCed them for comment (and dropped
the netdev CC).
No d-i udebs contain ipw2200 or ieee80211. The system
[dropping debian-boot from CC, they've indicated this isn't a
packaging issue for them at this time]
Hi,
Sorry for the confusion surround this, I was not at all aware
of the somewhat special state of ieee80211/ipw2200 upstream.
Let me answer some questions, now I have done a little bit or
On Fri, Nov 04, 2005 at 01:51:24AM -0500, Joey Hess wrote:
Horms wrote:
I don't have a particular problem with disabling those drivers from the
build. But the d-i guys might. I've CCed them for comment (and dropped
the netdev CC).
No d-i udebs contain ipw2200 or ieee80211. The system
On Fri, Nov 04, 2005 at 12:29:20PM +0900, Horms wrote:
do I take that comment to mean that upstream can't update the
drivers but Debian can? And if so, do you recommend updating
Debian's kernel packages, or putting the updates elsewhere?
Well, we could upstream, but so far no one is annoyed
On Wed, Nov 02, 2005 at 12:54:09PM +0600, Mikhail Gusarov wrote:
You ([EMAIL PROTECTED]) wrote:
I've encountered the problem with 2.6.14 kernels: they are shipped
with ancient version of ipw2200 drivers (1.0.0 while current
version is 1.0.7) and ancient version of ieee80211 subsystem
On Wed, Nov 02, 2005 at 04:26:21PM +, Christoph Hellwig wrote:
On Wed, Nov 02, 2005 at 12:54:09PM +0600, Mikhail Gusarov wrote:
So, having in mind the two levels of 'stablenesss': kernel
'stableness' and modules 'stableness' :) we should find the way to
exclude discussed modules from
On Wed, Nov 02, 2005 at 12:54:09PM +0600, Mikhail Gusarov wrote:
So, having in mind the two levels of 'stablenesss': kernel
'stableness' and modules 'stableness' :) we should find the way to
exclude discussed modules from the build, because in-kernel versions
will always be, erm..., slightly
21 matches
Mail list logo