From: Vitaly Bordug <vbordug@ru.mvista.com>
To: "antonio.dibacco" <antonio.dibacco@aruba.it>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: fs_enet on 2.4 and 8xx_immap
Date: Tue, 7 Mar 2006 16:55:22 +0300 [thread overview]
Message-ID: <20060307165522.7936fd7b@vitb.ru.mvista.com> (raw)
In-Reply-To: <20060307131500.3467.qmail@mx1.aruba.it>
On Tue, 07 Mar 2006 13:15:00 GMT
"antonio.dibacco" <antonio.dibacco@aruba.it> wrote:
> I think that to make it work I need to update cpm8xx_t inserting the fec2
> filed. Is this true? Could I use the 8xx_immap.h of a 2.6 kernel?
>
Not exactly. I think you can borrow the structures from 2.6, but do a triple-check that the result offsets are the same.
> Bye,
> Antonio.
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
>
--
Sincerely,
Vitaly
next prev parent reply other threads:[~2006-03-07 13:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 13:15 fs_enet on 2.4 and 8xx_immap antonio.dibacco
2006-03-07 13:55 ` Vitaly Bordug [this message]
2006-03-07 15:37 ` antonio.dibacco
2006-03-07 15:42 ` Vitaly Bordug
2006-03-07 15:49 ` antonio.dibacco
2006-03-07 16:18 ` Brent Cook
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=20060307165522.7936fd7b@vitb.ru.mvista.com \
--to=vbordug@ru.mvista.com \
--cc=antonio.dibacco@aruba.it \
--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