headers
Stefan Richter | 24 May 22:44
Picon

Changes to the FireWire kernel drivers in Linux 3.4

Hi all,

Linux kernel 3.4 has been released last Sunday.  These are the IEEE 1394
related changes:

<linux/firewire-cdev.h> API:
  - Added FW_CDEV_IOC_FLUSH_ISO ioctl which lets an application get any
    currently completed isochronous packets reported.  A corresponding
    libraw1394 update to use this ioctl in raw1394_iso_recv_flush() has
    been committed to libraw1394.git too and will show up in the next
    libraw1394 release.

firewire-core, -net, -ohci, -sbp2:
  - All messages to the kernel log are now consistently prefixed by driver
    name and device name or number.

firewire-ohci:
  - Fix premature completion of multichannel isochronous reception DMA.
    Also fixed in kernel 3.3.1, 3.2.14, 3.0.27.
  - Fix missing completion notification in isochronous I/O in case of big
    intervals between interrupt packets or with big packet headers.

firewire-sbp2:
  - If the target's unit directory contains a Unit_Unique_ID entry, use it
    instead of the node unique ID as the target's GUID in the ieee1394_id
    sysfs attribute and consequently in udev's /dev/disk/by-id symbolic
    links.
  - Do not try to log into targets on the local node. I/O to such targets
    is not yet implemented, and local targets are probably meant to be
    accessed by remote initiators anyway.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Stefan Richter | 24 May 21:14
Picon

[git pull] FireWire updates post v3.4

Linus,

please pull from the tag "firewire-updates" at

    git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git firewire-updates

to receive the following IEEE 1394 (FireWire) subsystem updates:

  - Fix mismatch between DMA mapping direction (was wrong) and DMA synchronization
    direction (was correct) of isochronous reception buffers of userspace drivers
    if vma-mapped for R/W access.  For example, libdc1394 was affected.

  - more consistent retry stategy in device discovery/ rediscovery, and improved
    failure diagnostics

  - various small cleanups, e.g. use SCSI layer's DMA mapping API in firewire-sbp2

The last few commits happened rather late for this pull request but I feel comfortable
with them.  ALSA firewire-lib changes were written by Clemens, hence are implicitly ACKed.

Axel Lin (1):
      firewire: use module_pci_driver

Clemens Ladisch (10):
      firewire: core: wait for inaccessible devices after bus reset
      firewire: core: improve reread_config_rom() interface
      firewire: move rcode_string() to core
      firewire: core: log error in case of failed bus manager lock
      firewire: core: log config rom reading errors
      firewire: core: fw_device_refresh(): clean up error handling
(Continue reading)

Permalink | Reply | 0 comments |
headers
Clemens Ladisch | 24 May 19:28
Picon
Gravatar

[PATCH 1/2] firewire: core: make address handler length 64 bits

The type of the length field of the fw_address_handler structure was
size_t, which restricted it to 32 bits on 32-bit architectures.

While making it u32 would match the userspace API, all calculations on
this field use 64 bits anyway, and the ability to use 4 GB or larger
address ranges is useful in the kernel.

Signed-off-by: Clemens Ladisch <clemens <at> ladisch.de>
---
 include/linux/firewire.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

--- a/include/linux/firewire.h
+++ b/include/linux/firewire.h
@@ -307,7 +307,7 @@ struct fw_transaction {

 struct fw_address_handler {
 	u64 offset;
-	size_t length;
+	u64 length;
 	fw_address_callback_t address_callback;
 	void *callback_data;
 	struct list_head link;

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
(Continue reading)

Permalink | Reply | 1 comment |
headers
Clemens Ladisch | 18 May 18:38
Picon
Gravatar

[PATCH 0/4] various SBP-2 DMA cleanups

 drivers/firewire/sbp2.c |   26 ++++++++------------------
 1 file changed, 8 insertions(+), 18 deletions(-)

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Permalink | Reply | 7 comments |
headers
Stefan Richter | 14 May 08:44
Picon

[Bug 43247] O2 micro SD/MMC+1394 controller: 1394 device can't work (Register access failure)

On May 14 bugzilla-daemon <at> bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=43247
> 
>            Summary: 1394 device can't work
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 2.6.38 and later
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: high
>           Priority: P1
>          Component: IEEE1394
>         AssignedTo: drivers_ieee1394 <at> kernel-bugs.osdl.org
>         ReportedBy: jennifer.li <at> o2micro.com
>         Regression: No
> 
> 
> Hi,
> 
> The 1394 initial process will fail and show " Apr  2 11:42:20 localhost kernel:
> firewire_ohci: Register access failure - please notify
> linux1394-devel <at> lists.sf.net".
> 
> This issue has happened in the O2 micro SD/MMC+1394 combo function chip + DELL
> platform Vans or Latitude E5520. We can find the same issue in J-micro USB+1394
> combo pci expresses card + DELL platform Vans or Latitude E5520.
> 
> We found the problem was caused by the initialization process. If the two
(Continue reading)

Permalink | Reply | 3 comments |
headers
Stefan Richter | 13 May 22:13
Picon

Re: [Bug 43244] New: firewire_ohci prevents boot

Rob,

thanks for the report.  Here is the full quote for the list to know. 
Some comments at the end.

On May 13 bugzilla-daemon <at> bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=43244
> 
>            Summary: firewire_ohci prevents boot
>            Product: Drivers
>            Version: 2.5
>     Kernel Version: 3.1.0-rc3
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: high
>           Priority: P1
>          Component: IEEE1394
>         AssignedTo: drivers_ieee1394 <at> kernel-bugs.osdl.org
>         ReportedBy: ra-kernel <at> hotmail.co.uk
>         Regression: Yes
> 
> 
> Created an attachment (id=73282)
>  --> (https://bugzilla.kernel.org/attachment.cgi?id=73282)
> lspci -vvv
> 
> After upgrading to a 3.2 series kernel (from 3.0 series), my laptop failed to
> boot. Retrying with nomodeset, the final message is:
(Continue reading)

Permalink | Reply | 9 comments |
headers
Stefan Richter | 11 May 20:44
Picon

libraw1394 plans

Hi all,

at the moment I would like to proceed with libraw1394 like this:

1. Add a copy of linux/firewire-{constants,cdev}.h to the libraw1394
sources in order to ensure that all features which a particular libraw1394
version supports are actually built, rather than silently disabled at
build time if older kernel headers are present.

2. Release libraw1394 v2.0.9.

3. Add an API to add a descriptor to the local Config ROM:
http://thread.gmane.org/gmane.linux.kernel.firewire.devel/14878/focus=14881

  - Do we want the remove-descriptor counterpart too, or would
    applications be satisfied with exit() or raw1394_destroy_handle() to
    do so?

4. Add an API which does the same as raw1394_read_cycle_timer() but lets
the user select a clock other than CLOCK_REALTIME (e.g. the monotonic
clock which is never reset by ntpd or other means to set the clock).
http://subversion.ffado.org/ticket/242

  - Should that new API stay with u_int64_t *local_time (microseconds,
    i.e. a like the struct timeval *tv argument of gettimeofday() but
    rolled out to tv_sec * 1000000 + tv_usec), or should we make use of
    the nanoseconds resolution that the underlying ioctl would offer, e.g.
    as struct timespec *tp like the respective argument of clock_gettime()?
    Even if nanoseconds resolution is not required by the application, the
    application might want to use clock_gettime() along with this new
(Continue reading)

Permalink | Reply | 3 comments |
headers
Clemens Ladisch | 3 May 15:05
Picon
Gravatar

Re: [FFADO-user] new laptop,bad FW chip (O2Micro)

Rick Green wrote:
> I've been having trouble with my old eMachines, that I seem to have
> concluded is a worn 4-pin ieee1394 connector, and not the software bugs as
> I have long suspected.

Please not that FireWire connectors are designed so that the cables
wear out first.  Did you try another cable?

> So yesterday I picked up a used Dell Vostro 1710 which is equipped with
> an 02Micro combined FW/SDRAM/MMC interface chip.  [...] dmesg reported
> discovering the device, but when I tried to start jackd, it started
> throwing errors.
> A first attempt to plug in a firewire external DVD burner failed, with a
> continuation of the same 'DMA context still active' messages that had
> started when I attempted to start jack.

It would be nice to see these messages.

A user on linux1394-devel reports that his O2 Micro controller doesn't
detect his HD unless it is already plugged in when the driver is loaded
(i.e., when the computer is booted).

> ...so I resorted to a reboot.  Here's a dmesg extract with interspersed
> comments on my trials:
>
> $ dmesg | grep firewire

Please use "grep -C3" to show surrounding lines.

> firewire_core: created device fw0: GUID 00000010a000b000, S400
(Continue reading)

Permalink | Reply | 1 comment |
headers
Stefan Richter | 2 May 23:02
Picon

ieee1394.wiki.kernel.org fully functional again

Hi all,

today, editing functionality of the wikis at kernel.org has been restored.
I will slowly update the ieee1394.wiki with current release notes, to-do
items etc. but everyone else is of course welcome to do so as well.
--

-- 
Stefan Richter
-=====-===-- -=-= ---=-
http://arcgraph.de/sr/

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Permalink | Reply | 0 comments |
headers
Stefan Richter | 1 May 13:14
Picon

Fw: [Bug 10935] fw-ohci: ALi M52xx unsupported

For the list to know:

Date: Tue, 1 May 2012 11:09:12 GMT
From: bugzilla-daemon <at> bugzilla.kernel.org
To: stefanr <at> s5r6.in-berlin.de
Subject: [Bug 10935] fw-ohci: ALi M52xx unsupported

https://bugzilla.kernel.org/show_bug.cgi?id=10935

Stefan Richter <stefanr <at> s5r6.in-berlin.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #15 from Stefan Richter <stefanr <at> s5r6.in-berlin.de>
2012-05-01 11:09:12 --- After a long while of using the PCI slots for
other cards, I put the Belkin F50508 back in yesterday in order to get
back to this bug again.

-------------------------------------------------------------------------
boot
-------------------------------------------------------------------------

Apr 30 20:38:16 stein kernel: pci 0000:0c:07.0: [10b9:5237] type 00 class 0x0c0310
Apr 30 20:38:16 stein kernel: pci 0000:0c:07.0: reg 10: [mem 0xfb7ff000-0xfb7fffff]
Apr 30 20:38:16 stein kernel: pci 0000:0c:07.0: PME# supported from D0 D1 D3hot D3cold
Apr 30 20:38:16 stein kernel: pci 0000:0c:07.1: [10b9:5237] type 00 class 0x0c0310
Apr 30 20:38:16 stein kernel: pci 0000:0c:07.1: reg 10: [mem 0xfb7fe000-0xfb7fefff]
(Continue reading)

Permalink | Reply | 0 comments |
headers
Sgt Larry Wayne | 28 Apr 10:40
Picon

Read Now

Hello,

My name is Staff Sergeant Larry Wayne with a desperate need for an mutual business proposal that will
benefit both of us, please get back to me if you are interested to hear
Sgt Larry Wayne

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Permalink | Reply | 0 comments |

Gmane