linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Ng <daniel.ng1234@gmail.com>
To: Laurent Pinchart <laurentp@cse-semaphore.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: How to bring up fs_enet on 2.6.27?
Date: Thu, 29 Jan 2009 11:42:31 +1100	[thread overview]
Message-ID: <547eba1b0901281642i7683e72fsd82233373d6bf858@mail.gmail.com> (raw)
In-Reply-To: <200901281050.44952.laurentp@cse-semaphore.com>

Thanks for your help so far Laurent-

On Wed, Jan 28, 2009 at 8:50 PM, Laurent Pinchart
<laurentp@cse-semaphore.com> wrote:
>
> Make sure FS_ENET_HAS_FCC is set in your kernel configuration.

Yep, I've done that...

>
> [snip]
>
>> The fs_enet probe() function doesn't seem to get called (I had put a
>> panic() in it). Should it?
>
> Yes it should.

Ok, so it isn't being called. What code calls the fs_enet probe()
function? What could be the reason why this isn't being called? ie. do
I need to set something else?

Should the device just be available as 'eth2', so that I can do
'ifconfig eth2 192.168.1.33'?

Cheers,
Daniel

  reply	other threads:[~2009-01-29  0:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28  5:04 How to bring up fs_enet on 2.6.27? Daniel Ng
2009-01-28  9:50 ` Laurent Pinchart
2009-01-29  0:42   ` Daniel Ng [this message]
     [not found] <mailman.5.1233190802.9523.linuxppc-dev@ozlabs.org>
2009-01-29  1:16 ` Mike Ditto
2009-02-19  6:47   ` Daniel Ng
2009-02-19 18:44     ` Scott Wood
2009-02-20  5:01       ` Daniel Ng
2009-02-25  7:09         ` Daniel Ng
2009-02-25  9:25           ` Mike Ditto
2009-02-27  6:41             ` Daniel Ng
2009-03-04 21:00           ` Scott Wood

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=547eba1b0901281642i7683e72fsd82233373d6bf858@mail.gmail.com \
    --to=daniel.ng1234@gmail.com \
    --cc=laurentp@cse-semaphore.com \
    --cc=linuxppc-dev@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).