On Sat, 14 Jan 2006 18:23:19 +0100, Lennert Buytenhek <[EMAIL PROTECTED]> wrote:
> On Sat, Jan 14, 2006 at 08:23:41AM -0800, Kris Katterjohn wrote:
>
> > This changes "signed long" to "long".
>
> Hmmm, is 'long' guaranteed to be signed?
Yes, it is. Only char can be signed or unsigned depending.
On Sat, 14 Jan 2006 15:13:39 +0100 (CET), Ulrich Kunitz <[EMAIL PROTECTED]>
wrote:
> [...] Register accesses in USB devices should be
> able to sleep. However the 80211 stacks I've seen so far have a
> fixed set of capabilities and do also assume, that at the driver
> layer everything can be done
From: Jeff Garzik <[EMAIL PROTECTED]>
Date: Sat, 14 Jan 2006 17:09:23 -0500
> A big open issue: should you fake ethernet, or represent 802.11
> natively throughout the rest of the net stack?
>
> The former causes various and sundry hacks, and the latter requires that
> you touch a bunch of non
On Sat, Jan 14, 2006 at 05:11:27PM -0500, Jeff Garzik wrote:
> John W. Linville wrote:
> >Since we are toying with the issue of multiple stacks (at least in the
> >wireless development kernels), some thought needs to be done w.r.t. how
> >to make a final decision between the two stacks. An object
On Sat, Jan 14, 2006 at 05:09:23PM -0500, Jeff Garzik wrote:
> John W. Linville wrote:
> >Other Issues
> >
>
> A big open issue: should you fake ethernet, or represent 802.11
> natively throughout the rest of the net stack?
>
> The former causes various and sundry hacks, and the lat
On Thu, Jan 05, 2006 at 10:04:44PM +0100, Lennert Buytenhek wrote:
> On Thu, Jan 05, 2006 at 01:57:07PM -0500, Jeff Garzik wrote:
>
> > >This patch removes the obsolete drivers/net/eepro100.c driver.
> > >
> > >Is there any known problem in e100 still preventing us from removing
> > >this driver
Count the total number of packets with collisions during transmission
in vp->stats.collisions.
Signed-off-by: Steffen Klassert <[EMAIL PROTECTED]>
--- vanilla-2.6.15/drivers/net/3c59x.c 2006-01-03 04:21:10.0 +0100
+++ linux-2.6.15-sk/drivers/net/3c59x.c 2006-01-14 17:54:16.0 +010
On Fri, 2006-01-13 at 17:19 -0500, John W. Linville wrote:
> Configuration
> =
>
> Configuration seems to be coalescing around netlink. Among other
> things, this technology provides for muliticast requests and
> asynchronous event notification.
>
> The kernel should provide generic
Hi,
Does netdevice_t serve any actual purpose now? It used to be for 2.2/2.4
compatibility, but we don't have that anymore.
Attached patch does a s/netdevice_t/struct net_device/g on all the files that
required it. It's against 20060114
cmn
--
Carlos Martín http://www.
> > > > > > > Have you tried enabling the NMI watchdog? Enable
> > CONFIG_X86_LOCAL_APIC and
> > > > > > > boot with `nmi_watchdog=1' on the command line, make sure that
> > the NMI line
> > > > > > > of /proc/interrupts is incrementing.
> > > > > > I'll give it a try. I've added it to the a
On Sat, 2006-01-14 at 10:46 +, Simon Kelley wrote:
> Chase Venters wrote:
>
> > As an aside to this whole thing, I know we're talking about *kernel*
> > wireless
> > but it's worthless to most people without good userland support as well.
> > Anyone have any thoughts and feelings on what th
John W. Linville wrote:
Actions
===
I need to establish a public git tree for wireless. I would like for
this to be on kernel.org, but I haven't got an account established
there yet. I've been dragging my feet a little, hoping that the
kernel.org account would materialize.
Since we are
John W. Linville wrote:
Other Issues
A big open issue: should you fake ethernet, or represent 802.11
natively throughout the rest of the net stack?
The former causes various and sundry hacks, and the latter requires that
you touch a bunch of non-802.11 code to make it aware of
Stuffed Crust wrote:
The hardware knows what frequencies it supports. Unfortunately this has
to be a somewhat dynamic thing, as this is often not queryable until the
device firmware is up and running.
This can be accomplished by passing a static table to the
register_wiphy_device() call (or
Hi Dave!
Please apply, thanks.
[NETFILTER] ip[6]t_policy: Fix compilation warnings
ip[6]t_policy argument conversion slipped when merging with x_tables
Signed-off-by: Benoit Boissinot <[EMAIL PROTECTED]>
Signed-off-by: Harald Welte <[EMAIL PROTECTED]>
--- a/net/ipv4/netfilter/ipt_policy.c 20
From: Al Viro
Sent: 1/14/2006 10:25:34 AM
> On Sat, Jan 14, 2006 at 09:38:44AM -0800, Kris Katterjohn wrote:
> > From: Lennert Buytenhek
> > Sent: 1/14/2006 9:23:19 AM
> > > Hmmm, is 'long' guaranteed to be signed?
> > >
> > > --L
> >
> > All integral types are except "char".
>
> That would get
On Thu, Jan 12, 2006 at 12:51:30AM +0100, Francois Romieu wrote:
> Marco Atzeri <[EMAIL PROTECTED]> :
> [...]
> > I hope to have not forgot something on the dump;
> > as before for 1469 and 1470 no ping reply.
>
> Thanks for your work. The status word did not appear.
> Can you apply the patch abov
On Sat, Jan 14, 2006 at 09:38:44AM -0800, Kris Katterjohn wrote:
> From: Lennert Buytenhek
> Sent: 1/14/2006 9:23:19 AM
>
> > On Sat, Jan 14, 2006 at 08:23:41AM -0800, Kris Katterjohn wrote:
> >
> > > This changes "signed long" to "long".
> >
> > Hmmm, is 'long' guaranteed to be signed?
> >
> >
Daniel,
some updates.
> I'll ask him about that.
> How can I find out which RF chip I have in my device? This is an area where I
> lack knowledge - why are there so many different chips? Is it one per region?
> Or maybe ZyDAS sell the ZD1211 but it has to be combined by other vendors with
> a RF
On Sat, 2006-14-01 at 16:24 +0200, Amnon Aaronsohn wrote:
> Hi,
>
> Here's a clearer description of the patch.
>
> Currently when PRIO is configured to use N bands, it lets the packets be
> directed to any of the bands 0..N-1. However, PRIO attaches a fifo qdisc
> only to the bands that appear in
From: Lennert Buytenhek
Sent: 1/14/2006 9:23:19 AM
> On Sat, Jan 14, 2006 at 08:23:41AM -0800, Kris Katterjohn wrote:
>
> > This changes "signed long" to "long".
>
> Hmmm, is 'long' guaranteed to be signed?
>
> --L
All integral types are except "char".
Kris
-
To unsubscribe from this list: s
On Sat, Jan 14, 2006 at 08:23:41AM -0800, Kris Katterjohn wrote:
> This changes "signed long" to "long".
Hmmm, is 'long' guaranteed to be signed?
--L
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://
This fixes some whitespace issues in net/core/filter.c
Signed-off-by: Kris Katterjohn <[EMAIL PROTECTED]>
Thanks!
--- x/net/core/filter.c 2006-01-14 10:06:40.0 -0600
+++ y/net/core/filter.c 2006-01-14 10:33:16.0 -0600
@@ -74,7 +74,6 @@ static inline void *load_pointer(struct
*
This changes "signed long" to "long".
Signed-off-by: Kris Katterjohn <[EMAIL PROTECTED]>
Thanks!
--- x/net/dccp/ackvec.c 2006-01-14 09:58:35.0 -0600
+++ y/net/dccp/ackvec.c 2006-01-14 10:17:24.0 -0600
@@ -144,7 +144,7 @@ static inline int dccp_ackvec_set_buf_he
WIRELESS_EXT < 18 will never be true in the kernel.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
drivers/net/wireless/tiacx/acx_struct.h |5
drivers/net/wireless/tiacx/common.c |4
drivers/net/wireless/tiacx/conv.c|2
drivers/net/wireless/tiacx/ioctl.c
WIRELESS_EXT < 18 will never be true in the kernel.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
drivers/net/wireless/ipw2100.c | 434 -
1 file changed, 434 deletions(-)
--- linux-2.6.15-rc3-mm1/drivers/net/wireless/ipw2100.c.old 2005-12-03
02:56:37
Hi,
Here's a clearer description of the patch.
Currently when PRIO is configured to use N bands, it lets the packets be
directed to any of the bands 0..N-1. However, PRIO attaches a fifo qdisc
only to the bands that appear in the priomap; the rest of the N bands
remain with a noop qdisc attached.
On Fri, 13 Jan 2006, John W. Linville wrote:
> Can the in-kernel stack be saved? With the addition of softmac?
> Is it possible to extend softmac to support virtual wlan devices?
> If not, how do we proceed?
I don't think, that we can continue with the current model of the
stacks. There appears
Folkert van Heusden <[EMAIL PROTECTED]> wrote:
>
> > > > > > Have you tried enabling the NMI watchdog? Enable
> CONFIG_X86_LOCAL_APIC and
> > > > > > boot with `nmi_watchdog=1' on the command line, make sure that the
> NMI line
> > > > > > of /proc/interrupts is incrementing.
> > > > > I'll
On Saturday 14 January 2006 00:03, you wrote:
> As an aside to this whole thing, I know we're talking about *kernel* wireless
> but it's worthless to most people without good userland support as well.
> Anyone have any thoughts and feelings on what things look like on the
> desktop? I think if w
Johannes Berg <[EMAIL PROTECTED]> writes:
> Yeah, this is about what I thought of -- and it makes me wonder if the
> stack really should be aware of the channelization, or if the WiPHY
> driver might better just handle it itself.
The latter, possibly using library functions from the stack :-)
--
On Fri, 13 Jan 2006, John W. Linville wrote:
> Configuration
> =
>
> At init, physical devices should be represented by a "WiPHY" device,
> not directly by a net_device. The list of physical devices should
> be discoverable through netlink and/or sysfs. (A WiPHY device is an
> abstr
Johannes Berg <[EMAIL PROTECTED]> writes:
> If you want the old userspace API to 'just work' you have to create one
> default wlan device at WiPHY init.
I'm not sure the old API is that important. This isn't something
programs (third party, kernel utils don't count) rely on. Most users
would swit
Hi,
> > > > > Have you tried enabling the NMI watchdog? Enable
> > > > > CONFIG_X86_LOCAL_APIC and
> > > > > boot with `nmi_watchdog=1' on the command line, make sure that the
> > > > > NMI line
> > > > > of /proc/interrupts is incrementing.
> > > > I'll give it a try. I've added it to the appe
Hi,
What's the real current status of your RFC2863 patch?
--
Krzysztof Halasa
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sat, 14 Jan 2006, Jeff Garzik wrote:
A new version of radvd has been released. There hasn't been any major
changes, just regular maintenance and a one new feature (jumboframe
support).
If it's in maintenance mode, why not call it version 1.0?
Perhaps the next version shall be :)
--
Pekk
Chase Venters wrote:
As an aside to this whole thing, I know we're talking about *kernel* wireless
but it's worthless to most people without good userland support as well.
Anyone have any thoughts and feelings on what things look like on the
desktop? I think if we work closely with some deskto
Pekka Savola wrote:
Hi,
A new version of radvd has been released. There hasn't been any major
changes, just regular maintenance and a one new feature (jumboframe
support).
If it's in maintenance mode, why not call it version 1.0?
Jeff
-
To unsubscribe from this list: send the li
On Fri, 2006-01-13 at 20:17 -0500, Stuffed Crust wrote:
> If you're talking about the former.. things get quite complicated, but
> that could be handled by having two WiPHY devices registered.
The former; and yes, I thought about that too -- having a driver that
shows two physical WiPHY devices
39 matches
Mail list logo
