From: Jochen Friedrich <jochen@scram.de>
To: rmcguire@videopresence.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 83xx HDLC Driver Dev - Multiple PHYs?
Date: Sat, 02 Feb 2008 21:36:46 +0100 [thread overview]
Message-ID: <47A4D45E.6030701@scram.de> (raw)
In-Reply-To: <000001c862fe$5ff16550$6405a8c0@absolut>
Hi Russell,
> I am putting support for multiple PHY's into the HDLC driver, but after
> converting it to use the of_device tree, and inserting a UCC@5000 for a
> single UCC HDLC driver, it occurred to me that if I insert more devices
> (UCC@6000, UCC@7000, UCC@8000) that the driver will attempt to load multiple
> times.
The module should only be loaded once. If the driver attempts to load multiple
times, this looks like a userscpace bug.
Thanks,
Jochen
next prev parent reply other threads:[~2008-02-02 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1201309203.24413.linuxppc-embedded@ozlabs.org>
2008-01-26 2:43 ` SET_NETDEV_DEV -> 83xx HDLC Driver?? Russell McGuire
2008-01-29 22:32 ` Andy Fleming
2008-01-29 23:04 ` Russell McGuire
2008-01-29 23:16 ` Scott Wood
2008-01-30 5:10 ` 83xx HDLC Driver Dev - Multiple PHYs? Russell McGuire
2008-02-02 20:36 ` Jochen Friedrich [this message]
2008-02-05 0:39 ` Andy Fleming
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=47A4D45E.6030701@scram.de \
--to=jochen@scram.de \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rmcguire@videopresence.com \
/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).