- 26 Apr, 2007 2 commits
-
-
Randy Dunlap authored
Make firewire entry points not 'extern': drivers/firewire/fw-device.c:160:25: warning: function 'fw_device_get' with external linkage has definition drivers/firewire/fw-device.c:167:13: warning: function 'fw_device_put' with external linkage has definition Signed-off-by:
Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by:
Stefan Richter <stefanr@s5r6.in-berlin.de>
-
Andrew Morton authored
You don't know what type is used to implement u64. Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Signed-off-by:
-
- 17 Apr, 2007 1 commit
-
-
Kristian Høgsberg authored
Signed-off-by:
Kristian Høgsberg <krh@redhat.com> Signed-off-by:
-
- 11 Apr, 2007 5 commits
-
-
Kristian Høgsberg authored
Signed-off-by:
-
Kristian Høgsberg authored
In some situations we can receive the ORB status write before we have received the ORB pointer write response. When this happens, we assume that the fw_transaction is finished and free the ORB struct containing the fw_transaction. This fix make the status write logic only accept status writes for ORBs where the initial ORB pointer write transaction finished. Signed-off-by:
-
Kristian Høgsberg authored
Or the SAM status codes from the device sense data into the command error code. Signed-off-by:
-
Kristian Høgsberg authored
Doh, bad typo... Signed-off-by:
-
Kristian Høgsberg authored
Signed-off-by:
-
- 28 Mar, 2007 9 commits
-
-
Kristian Høgsberg authored
Signed-off-by:
-
Kristian Høgsberg authored
Signed-off-by: -
Kristian Høgsberg authored
Some devices have a really long power-on cycle, and we fail to successfully probe these if they're plugged in and then turned on. There's really no down-side to bumping the number of retries and the retry delay, and most devices will get picked up within the first couple of retries anyway. Signed-off-by:
-
Kristian Høgsberg authored
In case the topology build fails, we want to retain the old topology info until another reset finishes and results in a valid new tree. If we clear card->irm_node to NULL and the topology build fails, we end up dereferencing a NULL pointer in a few places. Signed-off-by:
-
Kristian Høgsberg authored
Generalize the way we keep track of the various resources and assign a unique handle to each resource. Signed-off-by:
-
Kristian Høgsberg authored
Signed-off-by: -
Kristian Høgsberg authored
Make event struct layout common part include the closure and add a union for all event types; provide a mechanism for setting the bus reset event closure. Shuffle struct fw_cdev_queue_iso fields around to be 64-bit safe. Signed-off-by:
-
Kristian Høgsberg authored
Signed-off-by:
-
Kristian Høgsberg authored
We dynamically create an attribute group for the key present on the device in hand and point device->group to it. This way the device core adds the sysfs attributes for us as the device is added. Signed-off-by:
-
- 24 Mar, 2007 1 commit
-
-
Marc Butler authored
Signed-off-by:
Marc Butler <marc@adaptivecode.com> Signed-off-by:
-
- 21 Mar, 2007 3 commits
-
-
Kristian Høgsberg authored
Signed-off-by:
-
Kristian Høgsberg authored
We export the entire config rom, so this is technically redundant, but should make udev rules and HAL integration easier. Signed-off-by:
-
Kristian Høgsberg authored
The device_type struct is useful for setting attributes for a device and overriding .release and .uevent for a group of devices. This patch uses it this way to clean up the sysfs code a bit. Signed-off-by:
-
- 20 Mar, 2007 5 commits
-
-
Stefan Richter authored
Puts a stray endian annotation down. Signed-off-by: -
Stefan Richter authored
Signed-off-by:
-
Stefan Richter authored
as a precaution. Signed-off-by: -
Kristian Høgsberg authored
This serializes the update callback with the probe and remove callback from the driver core and prevents remove from being called while update is running for the same device. Signed-off-by:
-
Stefan Richter authored
to avoid confusion with CONFIG_FW_LOADER. Signed-off-by:
-
- 15 Mar, 2007 6 commits
-
-
Kristian Høgsberg authored
Signed-off-by:
-
Kristian Høgsberg authored
Signed-off-by:
-
Kristian Høgsberg authored
Signed-off-by:
-
Kristian Høgsberg authored
Signed-off-by:
-
Kristian Høgsberg authored
Setting these at create_context time or start_iso time doesn't matter much, but raw1394 sets them at start_iso time so that will be easier to emulate this way. Signed-off-by:
-
Kristian Høgsberg authored
The dualbuffer DMA setup did not account for the iso trailer word and thus didn't work correctly. With this fixed we can drop the dual buffer fallback mode. Signed-off-by:
-
- 09 Mar, 2007 8 commits
-
-
Kristian Høgsberg authored
Signed-off-by:
-
Kristian Høgsberg authored
Signed-off-by:
-
Kristian Høgsberg authored
Signed-off-by:
-
Kristian Høgsberg authored
Signed-off-by:
-
Kristian Høgsberg authored
Signed-off-by:
-
Kristian Høgsberg authored
Signed-off-by:
-
Kristian Høgsberg authored
Without this, pending transactions will dereference freed memory if they complete after the device file has been closed. Signed-off-by:
-
Kristian Høgsberg authored
The old async transmit context handling was starting and stopping DMA for every packet transmission. This could cause silently failing packet transmission, if the DMA was reprogrammed too close to being stopped. The general context code keeps DMA running at all times and fixes this problem. It's also a nice cleanup. Signed-off-by:
-
