LKML Archive on
help / color / mirror / Atom feed
From: Omar Schiaratura <>
Subject: sun neptune driver
Date: Tue, 19 Feb 2008 14:53:35 +0100	[thread overview]
Message-ID: <> (raw)

Hi all,
i'm trying to write a back-porting of the Sun neptune NIC driver(niu module) in kernel 2.6.24 to the kernel 2.6.20
because i need that driver in a xen linux environment.
The driver now compile and goes up clearly, NIC is configured, but doesn't work properly.
If i send packets to another machine with the same NIC and kernel 2.6.24,I saw with tcpdump that the packets was received and the answer was sent,
but at the other end (kernel 2.6.20 with my backported driver, and without XEN) nothing appens (tcpdump report sent packages, but i can't see anything sent from other side)
Do you have some tricks for me or can you suggest me something to do?

Some of the problem i encountered during port is that i can't find a function equivalent to compound_head, and if i port it to the source i can't find a way to use
an equivalent variable like page->first_page found in compound_head.
another proble was the folowing function:

static inline unsigned char *skb_transport_header(const struct sk_buff *skb)
        return (unsigned char *)((unsigned int)skb->head + (unsigned int)skb->h.raw);

that get the error: "error: invalid operands to binary +"
if i can't cast it in unsigned int, the same in skb_network_header (both back-ported from include/skbuff.h)


                 reply	other threads:[~2008-02-19 13:53 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:

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

  git send-email \ \ \ \
    --subject='Re: sun neptune driver' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).