On 12/3/07, David Woodhouse <[EMAIL PROTECTED]> wrote:
> From: Jon Smirl <[EMAIL PROTECTED]>
>
> The mpc5200 fec driver is corrupting memory. This patch fixes two bugs
> where the wrong skb was being referenced.
What does it take to get this patch into the kernel? I'v
On 11/9/07, Grant Likely <[EMAIL PROTECTED]> wrote:
> On 11/9/07, Domen Puncer <[EMAIL PROTECTED]> wrote:
> > On 09/11/07 00:31 -0500, Jon Smirl wrote:
> > > This is the reason I couldn't get user space started or connect to my
> > > nf
This is the reason I couldn't get user space started or connect to my
nfs server. Patch is against current linus git.
mpc5200 fec driver is corrupting memory. This patch fixes two bugs
where the wrong skb buffer was being referenced.
Signed-off-by: Jon Smirl <[EMAIL PROTECTED]>
--
On 9/28/07, Rick Jones <[EMAIL PROTECTED]> wrote:
> Herbert Xu wrote:
> > Jon Smirl <[EMAIL PROTECTED]> wrote:
> >
> >>App is writing seven bytes to the socket. Socket write timeout expires
> >>and the seven bytes are sent. The checksum is not getting
problem. e1000 is 192.168.1.4
64bit, Q6600. Dell Dimension 9200
Checksum is being computed ok for file copy traffic.
Problem was in rc7 too, I upgraded to current git to see if it was
fixed and it isn't
Wireshark is 0.99.4 from Ubuntu in case it is the problem.
--
Jon Smirl
[EMAIL PROT
On 9/19/07, Jon Smirl <[EMAIL PROTECTED]> wrote:
> This needs a cleanup too, but it is unrelated
Another set of related warnings that need clean up
CC drivers/spi/mpc52xx_psc_spi.o
drivers/spi/mpc52xx_psc_spi.c: In function 'mpc52xx_psc_spi_activate_cs
e_t'
drivers/serial/mpc52xx_uart.c: In function 'mpc52xx_uart_of_probe':
drivers/serial/mpc52xx_uart.c:978: warning: format '%lx' expects type
'long unsigned int', but argument 3 has type 'resource_size_t'
--
Jon Smirl
[EMAIL PROTECTED]
-
To unsubscribe from
>Uncompressing Kernel Image ... OK
>Booting using flat device tree at 0x40
>
> (No more output and boot is halted)
The root name of your device tree needs to match the name in pcm030.c
pcm030_probe(void). If they don't match this happens.
--
Jon Smirl
[EMAIL PROTECTED]
the
kernel doing DHCP and printing ... without a CR.
Two possible solutions, get rid of the link-up message or wait in in
the initial driver load until the link is up. Or we could leave it the
way it is, but some people may report this as a bug.
--
Jon Smirl
[EMAIL PROTECTED]
-
To unsubsc
i++)
mpc52xx_fec_mac_addr[5-i] = val64 >> (i*8);
return 0;
}
__setup("mpc52xx-mac=", mpc52xx_fec_mac_setup);
--
Jon Smirl
[EMAIL PROTECTED]
-
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
==
> --- linux.git.orig/drivers/net/phy/phy.c
> +++ linux.git/drivers/net/phy/phy.c
> @@ -409,6 +409,7 @@ int phy_mii_ioctl(struct phy_device *phy
>
> return 0;
> }
> +EXPORT_SYMBOL(phy_mii_ioctl);
>
> /**
> * phy_start_aneg - start auto-negotiation for this PHY device
>
to review that way. The bestcomm and dts changes
> don't need to go to the netdev list.
A similar patch that is already broken up is available for Efika.
http://dev.gentoo.org/~nixnut/efika/efika-patches-2.6.22.tar.bz2
--
Jon Smirl
[EMAIL PROTECTED]
-
To unsubscribe from this list: se
the kernel GPL'd if the author doesn't
explicitly grant them more liberal BSD license in addition?
The problem then comes in taking the patches that were only made
available against GPL code and reshipping them under the BSD license
without the author explicitly agreeing to this.
Wha
7;t a patch against the kernel have to be GPL? When these
patches get pulled back into BSD and distributed with it, did BSD get
infected with the GPL? AFAIK this has never been legally sorted out.
--
Jon Smirl
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe
On 1/23/07, Michael Wu <[EMAIL PROTECTED]> wrote:
On Tuesday 23 January 2007 18:23, Jon Smirl wrote:
> I have to manually associate the dscape stack with my AP. Is this way
> the code is supposed to work? Everything works ok after the manual
> association.
>
It'
On 1/23/07, Michael Wu <[EMAIL PROTECTED]> wrote:
On Tuesday 23 January 2007 18:23, Jon Smirl wrote:
> I have to manually associate the dscape stack with my AP. Is this way
> the code is supposed to work? Everything works ok after the manual
> association.
>
It'
I have to manually associate the dscape stack with my AP. Is this way
the code is supposed to work? Everything works ok after the manual
association.
Is there documentation for this stack? Any special utilities for it?
I'd like to get my devices operating in master mode.
--
Jon Smirl
[
On 1/23/07, Michael Wu <[EMAIL PROTECTED]> wrote:
On Tuesday 23 January 2007 12:10, Jon Smirl wrote:
> I've hit this twice. This time I unplugged my USB hub which had the
> device in it.
>
Please try the patch I posted earlier:
http://marc.theaimsgroup.com/?l=linux-netdev&a
development of a software based 802.11s
stack?
--
Jon Smirl
[EMAIL PROTECTED]
-
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 1/23/07, Dan Williams <[EMAIL PROTECTED]> wrote:
On Tue, 2007-01-23 at 12:14 -0500, Jon Smirl wrote:
> On 1/23/07, Johannes Berg <[EMAIL PROTECTED]> wrote:
> > On Tue, 2007-01-23 at 11:18 -0500, Jon Smirl wrote:
> >
> > > Is the 802.11s Draft 1.0 spec pu
On 1/23/07, Johannes Berg <[EMAIL PROTECTED]> wrote:
On Tue, 2007-01-23 at 11:18 -0500, Jon Smirl wrote:
> Is the 802.11s Draft 1.0 spec publicly available yet? It is supposed
> to be making changes at the very lowest MAC layers. It will be hard to
> be compatible with that
ernel: ===
--
Jon Smirl
[EMAIL PROTECTED]
-
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 1/23/07, Johannes Berg <[EMAIL PROTECTED]> wrote:
On Mon, 2007-01-22 at 10:20 -0500, Jon Smirl wrote:
> What is the general solution for 802.11s?
None yet.
> I'm working on an embedded
> design that would benefit from 11s support and I'd rather not have to
> rol
I need to design onto my board given
that the 8388 is not available general consumption. My system has
plenty of power and CPU available so a softmac type 11s solution is
the most cost effective. It seems to me that the design of a software
based 11s stack should be coordinated with the 8388 firmwa
e 8388 hardware implementation?
--
Jon Smirl
[EMAIL PROTECTED]
-
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
25 matches
Mail list logo
