Dear Kentaro,
- netperf -H
192.168.1.1 -t TCP_STREAM 110 Mbps netperf -H 192.168.1.1 -t UDP_STREAM
210 Mbps -
Are these results the ones with or without Jumbo-frame
Hi,
Could I store both, hw bitstream and kernel, in the xilinx platform flash ?
i think its not bit enough. I want to store the hw bitstream in the
platform flash as usual and the kernel in the additional flash. I don't
know how to store the kernel in the flash until know. This why I
Jon Smirl wrote:
On 11/7/07, Matt Sealey [EMAIL PROTECTED] wrote:
Jon Smirl wrote:
I'm not in favor of all these fsl prefixes. These chip families
do get sold. What would we have done with intel,pxa320 all over
the place when they sold it to marvell? mass changes to
marvell,pxa320?
That's
Hi,
Yes, for 1500 MTU these aren’t too bad. One thing to note, using the
TCP_STREAM option does not take advantage of zero-copy and possibly checksum
offload on the transmit side. You should use the TCP_SENDFILE option for that.
We typically use options such as:
netperf
Hi all,
I finished the main part of porting u-boot 1.3 rc3 to our custon 8548
board and am now trying to boot our 2.6.22 kernel and device tree:
= bootm 100 - c0
## Booting image at 0100 ...
Image Name: Linux-2.6.22.2
Image Type: PowerPC Linux Kernel Image (gzip compressed)
On 11/8/07, Scott Wood [EMAIL PROTECTED] wrote:
Jon Smirl wrote:
On 11/7/07, Matt Sealey [EMAIL PROTECTED] wrote:
Jon Smirl wrote:
I'm not in favor of all these fsl prefixes. These chip families
do get sold. What would we have done with intel,pxa320 all over
the place when they sold it
When a module has relocation sections with tens of thousands worth of entries,
counting the distinct/unique entries only (i.e. no duplicates) at load time can
take tens of seconds and up to minutes. The sore point is the count_relocs()
function which is called as part of the architecture specific
Jon Smirl wrote:
On 11/8/07, Scott Wood [EMAIL PROTECTED] wrote:
As far as I know the only dts using vendor prefixes in the compatible
attributes is 5200lite one for the gpt entries. Everything else will
need to be changed.
Look a little harder. Many of the Freescale boards/devices do it
Jon Smirl wrote:
No one has answered this yet. It makes no sense at all to mix use of
the vendor prefix on some compatible entries and not on others. The
syntax of compatible entries needs to be consistent.
Right, the vendor prefix should always be used. Not all of the existing
trees are
On 11/8/07, Matt Sealey [EMAIL PROTECTED] wrote:
Jon Smirl wrote:
On 11/8/07, Scott Wood [EMAIL PROTECTED] wrote:
I think you may be placing too much faith in the vendors.
Is a 7400 a Freescale powerpc chip, or a quad 2-input NAND gate? :-)
There has to be more to the part number for
Jon Smirl wrote:
On 11/8/07, Scott Wood [EMAIL PROTECTED] wrote:
I think you may be placing too much faith in the vendors.
Is a 7400 a Freescale powerpc chip, or a quad 2-input NAND gate? :-)
There has to be more to the part number for the Freescale powerpc chip
than just 7400. 7400 is a
On 11/8/07, Scott Wood [EMAIL PROTECTED] wrote:
Jon Smirl wrote:
No one has answered this yet. It makes no sense at all to mix use of
the vendor prefix on some compatible entries and not on others. The
syntax of compatible entries needs to be consistent.
Right, the vendor prefix should
Matt Sealey wrote:
The orderable part numbers add 3 or 4 characters to the front and about
8 after. There is a difference between MPC7400 and PPC7400, and the
low voltage versions, and the different clock speeds. Orderable part
number for a recent G4 might be PPC7448B1333NL -
Yeah, part,
No one has answered this yet. It makes no sense at all to mix use of
the vendor prefix on some compatible entries and not on others. The
syntax of compatible entries needs to be consistent.
On 11/7/07, Jon Smirl [EMAIL PROTECTED] wrote:
On 11/7/07, Matt Sealey [EMAIL PROTECTED] wrote:
Jon
On 11/8/07, Jon Smirl [EMAIL PROTECTED] wrote:
No one has answered this yet. It makes no sense at all to mix use of
the vendor prefix on some compatible entries and not on others. The
syntax of compatible entries needs to be consistent.
The 5200 binding is poorly done on this point. I've got
On 11/8/07, Scott Wood [EMAIL PROTECTED] wrote:
Jon Smirl wrote:
On 11/8/07, Scott Wood [EMAIL PROTECTED] wrote:
As far as I know the only dts using vendor prefixes in the compatible
attributes is 5200lite one for the gpt entries. Everything else will
need to be changed.
Look a little
Jon Smirl wrote:
On 11/8/07, Scott Wood [EMAIL PROTECTED] wrote:
Several hundred? I don't think there are several hundred unique
property names or compatible entries in arch/powerpc/boot/dts *total*,
There are 601 'compatible' attributes in the directory.
I said unique. And there do
Hi,
I am currently working on a MPC8540-based custom board, which runs Linux
2.6.15 (arch/ppc).
I set up a periodically running kernel thread, which is delayed for a
single jiffy using schedule_timeout() in an infinite loop. It is used to
measure delays between invocations of that thread. For
On Sat, 03 Nov 2007 20:16:36 +0100 Jochen Friedrich [EMAIL PROTECTED] wrote:
Subject: [PATCH] [POWERPC] Fix typo #ifdef - #ifndef
Please put the powerpc outside the []. Because things inside [] get
removed when the receiver applies the patch, but the subsystem
identification (powerpc) is
19 matches
Mail list logo
