mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Robin Cook <rcook@wyrms.net>
To: linux-kernel@vger.kernel.org
Subject: Issue with firewire from 2.6.35.9 to 2.6.36.1
Date: Sun, 05 Dec 2010 17:37:06 -0600	[thread overview]
Message-ID: <1291592226.7134.1.camel@pheuri.wyrms.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1604 bytes --]

Hello,

I recently upgraded from 26.35.9 to 2.6.36.1 and now the /dev/fwX
devices are not being created.  I have udev 164 installed.

2.6.35.9 dmesg firewire lines...

firewire_ohci 0000:07:00.0: PCI INT A -> GSI 44 (level, low) -> IRQ 44
firewire_ohci 0000:07:00.0: setting latency timer to 64
firewire_ohci: Added fw-ohci device 0000:07:00.0, OHCI v1.10, 4 IR + 8 IT contexts, quirks 0x1
firewire_core: created device fw0: GUID 0010dc0001adc862, S400
firewire_core: created device fw1: GUID 00808803072803a5, S100
firewire_core: phy config: card 0, new root=ffc1, gap_count=5

2.6.36.1 dmesg firewire lines...

firewire_ohci 0000:07:00.0: PCI INT A -> GSI 44 (level, low) -> IRQ 44
firewire_ohci 0000:07:00.0: setting latency timer to 64
firewire_ohci 0000:07:00.0: irq 75 for MSI/MSI-X
firewire_ohci: Added fw-ohci device 0000:07:00.0, OHCI v1.10, 4 IR + 8 IT contexts, quirks 0x1

I have compared the difference between the two kernel configs and the
only differences that I see that may apply to the firewire are:

 CONFIG_DNOTIFY=y
-CONFIG_INOTIFY=y
 CONFIG_INOTIFY_USER=y

 # CONFIG_IEEE1394 is not set 
+CONFIG_FIREWIRE_NOSY=m  
 CONFIG_I2O=m

On the ieee1394 wiki page it says that these kernel option are expected
to be on for the libraw1394:

CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_EPOLL=y

These option are correct in the 2.6.35.9 kernel but the CONFIG_INOTIFY
option is missing completely in the 2.6.36.1 kernel.

Is this a change in how the firewire works in the kernel and that udev
needs to be modified or is there something else wrong?

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2010-12-06  0:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-05 23:37 Robin Cook [this message]
2010-12-06  0:11 ` Maxim Levitsky
2010-12-06  7:29   ` Stefan Richter
2010-12-06  9:40     ` Clemens Ladisch
2010-12-06 22:04     ` Robin Cook
2010-12-07  8:27       ` Stefan Richter
2010-12-07  9:17         ` Clemens Ladisch
2010-12-07 14:04           ` Stefan Richter
2011-01-08 10:16       ` Stefan Richter

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=1291592226.7134.1.camel@pheuri.wyrms.net \
    --to=rcook@wyrms.net \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®