From: Felipe Contreras <felipe.contreras@gmail.com>
To: Ameya Palande <ameya.palande@nokia.com>
Cc: Omar Ramirez Luna <omar.ramirez@ti.com>,
linux-omap <linux-omap@vger.kernel.org>,
"Doyu Hiroshi (Nokia-D/Helsinki)" <hiroshi.doyu@nokia.com>,
"Contreras Felipe (Nokia-D/Helsinki)"
<felipe.contreras@nokia.com>, Nishanth Menon <nm@ti.com>
Subject: Re: [PATCH 0/2] dspbridge: reorganize initialization and probe
Date: Wed, 9 Jun 2010 12:28:59 +0300 [thread overview]
Message-ID: <AANLkTik1fLQMSGEZb3RXzNeV6mXaDESkj_pLkhheRrAb@mail.gmail.com> (raw)
In-Reply-To: <1276073342.10359.0.camel@chotu>
On Wed, Jun 9, 2010 at 11:49 AM, Ameya Palande <ameya.palande@nokia.com> wrote:
> On Wed, 2010-06-09 at 09:25 +0200, ext Felipe Contreras wrote:
>> On Wed, Jun 9, 2010 at 3:48 AM, Omar Ramirez Luna <omar.ramirez@ti.com> wrote:
>> > Split the functions to have cleaner error handling paths, this
>> > will aslo cover a case where bridge initialization has failed but
>> > device entry is still available which leads to unknown behavior.
>>
>> Great, I was wondering why this was not the case.
>>
>> Now that you are on this, do you know if there's something missing in
>> order to automatically load the module when somebody tries to open
>> /dev/DspBridge?
>
> I thought /dev/DspBridge will only appear if you load the module ;)
Kind of...
$ sudo touch /dev/DspBridge
See? I have dspbridge on my laptop ;)
I think it's possible to have udev rules that create the file, and
automatically load the module when accessed, but I don't know much
about udev.
--
Felipe Contreras
next prev parent reply other threads:[~2010-06-09 9:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 0:48 [PATCH 0/2] dspbridge: reorganize initialization and probe Omar Ramirez Luna
2010-06-09 0:48 ` [PATCH 1/2] DSPRBIDGE: split probe from bridge initializations Omar Ramirez Luna
2010-06-09 0:48 ` [PATCH 2/2] DSPBRIDGE: reorganize probe function Omar Ramirez Luna
2010-06-09 7:25 ` [PATCH 0/2] dspbridge: reorganize initialization and probe Felipe Contreras
2010-06-09 8:49 ` Ameya Palande
2010-06-09 9:28 ` Felipe Contreras [this message]
2010-06-14 17:59 ` Ramirez Luna, Omar
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=AANLkTik1fLQMSGEZb3RXzNeV6mXaDESkj_pLkhheRrAb@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=ameya.palande@nokia.com \
--cc=felipe.contreras@nokia.com \
--cc=hiroshi.doyu@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=omar.ramirez@ti.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).