From: jacopo mondi <j.mondi@voltaelectronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] building enc28j60 for omap3: undefined references
Date: Thu, 17 Feb 2011 11:48:51 +0100 [thread overview]
Message-ID: <20110217114851.5b679230@BlackBox> (raw)
In-Reply-To: <4D5CF3C0.5050908@denx.de>
On Thu, 17 Feb 2011 11:09:04 +0100
Stefano Babic <sbabic@denx.de> wrote:
> And the driver builds fine with beagleboard, too. Do you drop the
>
> #undef CONFIG_CMD_NET
>
> in the beagleboard configuration file ? If not, this generates exactly
> the error you report.
>
> Best regards,
> Stefano Babic
>
GOSH, I've exactly searched through the code for CONFIG_CMD_NET, but I
did not noticed was an undef statment instead of a define!
Everything's fine now. Thank you.
Just another question. I've studied the linux enc28j60 driver and
noticed it features an interrupt driven work flow.
No interrupt are used in u-boot version (for what I've seen). Is it
based on some sort of polling instead of interrupt? Isn't
that dangerous? I mean, if there are no data available everything is
going to freeze..
Thank you all
jacopo
next prev parent reply other threads:[~2011-02-17 10:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 16:29 [U-Boot] building enc28j60 for omap3: undefined references jacopo mondi
2011-02-16 17:31 ` Reinhard Meyer
2011-02-17 5:48 ` Mike Frysinger
2011-02-17 9:35 ` jacopo mondi
2011-02-17 10:09 ` Stefano Babic
2011-02-17 10:48 ` jacopo mondi [this message]
2011-02-17 12:37 ` Stefano Babic
2011-02-18 13:12 ` jacopo mondi
2011-02-22 16:34 ` [U-Boot] building enc28j60 for omap3: SILICON ERRATA jacopo mondi
2011-02-23 22:32 ` Anatolij Gustschin
2011-02-23 23:32 ` Wolfgang Denk
2011-02-25 8:37 ` jacopo mondi
2011-03-02 14:08 ` [U-Boot] building enc28j60 for omap3: (omap3_spi rxtx) jacopo mondi
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=20110217114851.5b679230@BlackBox \
--to=j.mondi@voltaelectronics.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.