linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Russell McGuire" <rmcguire@videopresence.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: NETdev driver question xxxx_type_trans()
Date: Fri, 22 Feb 2008 12:26:12 -0800	[thread overview]
Message-ID: <000001c87591$2b5a8740$6405a8c0@absolut> (raw)

[-- Attachment #1: Type: text/plain, Size: 949 bytes --]

All,

A general and specific question on the behavior of netdev devices before
received sk_buff(s) get passed up to the kernel.

I am almost done creating / testing an HDLC device driver for the 83xx.

I have it working at a low level and was printing out skb_bufs before and
after TX and RX, to ensure data integrity.

Due to me having the print_skbbuf, AFTER the hdlc_type_trans(skb, ndev).
I thought I was continuously losing 14 bytes of data, after a little digging
I realized that the hdlc_type_trans() call
was shifting the skb->data pointer forward by 14 bytes. ????????

Is this corresponding to a 14 byte pad that the kernel stack adds before it
sends it down?
And why isn't the data length being shortened as a result after I call
hdlc_type_trans?

Anyway. I guess I am confused as to what this function was intended for, I
see there are other calls for eth_type_trans, so I imagine their usage is
similar. 

When are they needed?

-Russ


[-- Attachment #2: Type: text/html, Size: 7130 bytes --]

             reply	other threads:[~2008-02-22 20:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-22 20:26 Russell McGuire [this message]
2008-02-22 20:39 ` NETdev driver question xxxx_type_trans() Andy Fleming
2008-02-22 23:48   ` Russell McGuire

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='000001c87591$2b5a8740$6405a8c0@absolut' \
    --to=rmcguire@videopresence.com \
    --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;
as well as URLs for NNTP newsgroup(s).