public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcus Ramos <marcus@ansp.br>
To: linux-kernel@vger.kernel.org
Subject: Making changes to 3c90X.c
Date: Mon, 05 Mar 2001 16:44:35 -0300	[thread overview]
Message-ID: <3AA3ECA3.55A05B8B@ansp.br> (raw)

Hello,

I am developing an application for which I need to make small changes to
the source code of 3c90x.c (3com ethernet driver). Indeed, I need to
access - and modify - the contents of the packets right before they are
sent on the wire. After examining sk_buff.h, function NICSendPacket of
3c90x.c and reading chapter 14 (Network Drivers) of the book Linux
Device Drivers, I concluded that SocketBuffer->data points to the first
octet of data in the packet.

My question is: can I access the contents of the buffer simply by

*(SocketBuffer->data)
*(SocketBuffer->data+1)
*(SocketBuffer->data+2) etc ?

What is the layout of the octets starting at data ? Eth header, IP
header, TCP header etc ,or ?

Can I write new contents back to the buffer the same way ?

Thanks in advance,
Marcus.



                 reply	other threads:[~2001-03-05 19:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3AA3ECA3.55A05B8B@ansp.br \
    --to=marcus@ansp.br \
    --cc=linux-kernel@vger.kernel.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