LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: zDL Linux PPC <linuxppc@4bridgeworks.com>
To: 'Gerhard Jaeger' <g.jaeger@sysgo.com>
Cc: zML Linux PPC Dev <linuxppc-dev@ozlabs.org>,
	zML Linux PPC Embedded <linuxppc-embedded@ozlabs.org>
Subject: RE: Power PC 440GX Jumbo Packets EMAC2/3
Date: Thu, 24 Feb 2005 13:55:33 -0000	[thread overview]
Message-ID: <C18BA5DDB58DD511BD0700C0DF0DD450294288@NTSERVER4> (raw)

Gerhard,

> [SNIPSNAP]
> > > > Any suggestions on how to overcome this problem??? My only 
> > > idea is to either
> > > > add data to the packet (don't think this will work) or 
> > > forceably fragment
> > > > the packet (if it is 2K in size) to ensure that it never 
> > > uses the exact size
> > > > of the tx fifo.....
> > > 
> > > Have you applied Matt Porters patch? It has been submitted at 
> > > the beginning
> > > of this month?
> > 
> > No I haven't seen it on either of these lists, do you know 
> where I can find
> > it 
> > 
> > Thanks
> 
> Browse the linuxpp-embedded archive list, I think it was 
> around the 9th
> of february...
> or try this one
> http://ozlabs.org/pipermail/linuxppc-embedded/2005-February/00
1260.html

Thanks for this however it is not the problem I am experiencing at present,
my problem is with the TX and not the RX side of things, I have added debug
and the ibm_emac_core prints out that the packet has been transmitted,
however I see nothing at the other end when you transmit a packet of tx fifo
size bytes from the PPC 440 GX, packets of <tx fifo size or >tx fifo size
are transmitted fine from the PPC 440 GX, so long as you do not transmit a
packet of Tx fifo size.

Thanks

             reply	other threads:[~2005-02-24 13:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-24 13:55 zDL Linux PPC [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-24 13:12 Power PC 440GX Jumbo Packets EMAC2/3 zDL Linux PPC
2005-02-24 13:45 ` Gerhard Jaeger
2005-02-24 11:46 zDL Linux PPC
2005-02-24 12:19 ` Gerhard Jaeger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=C18BA5DDB58DD511BD0700C0DF0DD450294288@NTSERVER4 \
    --to=linuxppc@4bridgeworks.com \
    --cc=g.jaeger@sysgo.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox