14 but AXI CAN 5.0 seems to only go up to 11.
Or maybe it is undocumented or there is a newer version somewhere?
[1]
https://www.xilinx.com/support/documentation/ip_documentation/can/v5_0/pg096-can.pdf
--
Anssi Hannula / Bitwise Oy
+358 503803997
/kernel/git/torvalds/linux.git/commit/?id=b88a105802e9aeb6e234e8106659f5d1271081bb
--
Anssi Hannula / Bitwise Oy
/kernel/git/torvalds/linux.git/commit/?id=b88a105802e9aeb6e234e8106659f5d1271081bb
--
Anssi Hannula / Bitwise Oy
e
like month and day got swapped for some reason.
Not a big issue I guess, but worth looking into if it is something in
your workflow causing this :)
Noticed these strange Dates while looking at Greg's stable-queue repo.
--
Anssi Hannula
--
To unsubscribe from this list: send the line "unsubscrib
into if it is something in
your workflow causing this :)
Noticed these strange Dates while looking at Greg's stable-queue repo.
--
Anssi Hannula
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
efore calling cell_defer().
Incoming bios for that block will then be detained in the cell and
released only after clear_dirty() has completed, so the race will not
occur.
Found by inspecting the code after noticing spurious dirty counts
(scenario B).
Signed-off-by: Anssi Hannula
Cc: Joe Thor
cell_defer().
Incoming bios for that block will then be detained in the cell and
released only after clear_dirty() has completed, so the race will not
occur.
Found by inspecting the code after noticing spurious dirty counts
(scenario B).
Signed-off-by: Anssi Hannula anssi.hann...@iki.fi
Cc: Joe Thornber
ith
>>
>> -- Begin forwarded Message --
>>
>>
>> nr_dirty is updated without locking, causing it to drift so that it is
>> non-zero (either a small positive integer, or a very large one when an
>> underflow occurs) even when there are no actual dirty
(either a small positive integer, or a very large one when an
underflow occurs) even when there are no actual dirty blocks.
Fix that by using an atomic type for nr_dirty.
Signed-off-by: Anssi Hannula anssi hannula iki fi
Cc: Joe Thornber ejt redhat com
Cc: stable vger kernel org
---
So
> Is there any guideline I should stick to I am
> not aware of?
Only "3.7 Dynamic update of an effect" of input/ff.txt.
--
Anssi Hannula
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.or
developers with this
information, you should put it in generic documentation ("it is not
guaranteed that X", etc.). If not, don't say "for userspace developers".
[...]
> diff --git a/drivers/input/ff-memless-next.c b/drivers/input/ff-memless-next.c
> new file mode 100644
| 11 +
> drivers/input/Makefile | 1 +
> drivers/input/ff-memless-next.c | 789
>
> include/linux/input/ff-memless-next.h | 32 ++
> 7 files changed, 1033 insertions(+), 36 deletions(-)
> --
> 1.9.0
&
/drivers/input/ff-memless-next.c
@@ -0,0 +1,789 @@
+/*
+ * Force feedback support for memoryless devices
+ *
+ * This module is based on ff-memless orignally written by Anssi Hannula.
+ * It is extended to support all force feedback effects currently supported
+ * by the Linux input stack
/input/ff-memless-next.h | 32 ++
7 files changed, 1033 insertions(+), 36 deletions(-)
--
1.9.0
--
--
Anssi Hannula
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
update of an effect of input/ff.txt.
--
Anssi Hannula
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
01.11.2013 13:29, Rafał Miłecki kirjoitti:
> 2013/11/1 Anssi Hannula :
>>> Both are working for me. I've tested it using 2 movies:
>>> 1) English TrueHD.5.1 @ 1417 kbps
>>> 2) Audio
>>> Codec: DTSHD-MA
>>> Bitrate...
01.11.2013 13:29, Rafał Miłecki kirjoitti:
2013/11/1 Anssi Hannula anssi.hann...@iki.fi:
Both are working for me. I've tested it using 2 movies:
1) English TrueHD.5.1 @ 1417 kbps
2) Audio
Codec: DTSHD-MA
Bitrate..: 3718 kbps
kHz/bit..: 24-bit
01.11.2013 01:51, Rafał Miłecki kirjoitti:
> 2013/11/1 Anssi Hannula :
>> Just to check, is the display mode 720p50 or higher (as per HDMI spec
>> 7.3.3)? Though I guess too small mode would cause something else, not
>> this...
>
> I'm using 1080p
01.11.2013 01:25, Rafał Miłecki kirjoitti:
> 2013/10/31 Anssi Hannula :
>>> But I can hear sound for rear right and rear left only :(
>>>
>>> Is there anything more I can provide to help resolve this? Do you have
>>> any idea how we can resolve this?
>&g
31.10.2013 18:22, Rafał Miłecki kirjoitti:
> 2013/10/30 Anssi Hannula :
>> BTW, there is a newer version (which was actually applied) of this patchset
>> in alsa-devel@, seems you were missing from CC on that one.
>
> I didn't try that updated version yet, but I'm afrai
31.10.2013 18:22, Rafał Miłecki kirjoitti:
2013/10/30 Anssi Hannula anssi.hann...@iki.fi:
BTW, there is a newer version (which was actually applied) of this patchset
in alsa-devel@, seems you were missing from CC on that one.
I didn't try that updated version yet, but I'm afraid I discovered
01.11.2013 01:25, Rafał Miłecki kirjoitti:
2013/10/31 Anssi Hannula anssi.hann...@iki.fi:
But I can hear sound for rear right and rear left only :(
Is there anything more I can provide to help resolve this? Do you have
any idea how we can resolve this?
According to the below the receiver
01.11.2013 01:51, Rafał Miłecki kirjoitti:
2013/11/1 Anssi Hannula anssi.hann...@iki.fi:
Just to check, is the display mode 720p50 or higher (as per HDMI spec
7.3.3)? Though I guess too small mode would cause something else, not
this...
I'm using 1080p all the time. Do you think
Rafał Miłecki kirjoitti 2013-10-30 17:35:
2013/10/1 Anssi Hannula :
ATI/AMD codecs do not support all the standard HDA HDMI/DP functions,
instead various vendor-specific verbs are provided.
I've just tried my HD6970M (BARTS, DCE5) in my Samsung NP700G7A-S01PL.
cat /proc/asound/card1/eld#0.0
Rafał Miłecki kirjoitti 2013-10-30 17:35:
2013/10/1 Anssi Hannula anssi.hann...@iki.fi:
ATI/AMD codecs do not support all the standard HDA HDMI/DP functions,
instead various vendor-specific verbs are provided.
I've just tried my HD6970M (BARTS, DCE5) in my Samsung NP700G7A-S01PL.
cat /proc
eaker-test -D hdmi:CARD=Generic,DEV=0,AES0=0x06 -c2 -r48000
o Also, is there a difference in the beginning of these
(maybe garbage sound and/or slightly slower startup?):
aplay -Dhdmi:CARD=Generic,DEV=0,AES0=4 -r44100 -f s16_le -c2
testi.dts.cut.spdif
aplay -Dhdmi:CARD=Generic,DEV=0,AES
-Dhdmi:CARD=Generic,DEV=0,AES0=4 -r44100 -f s16_le -c2
testi.dts.cut.spdif
aplay -Dhdmi:CARD=Generic,DEV=0,AES0=6 -r44100 -f s16_le -c2
testi.dts.cut.spdif
o Contents of /proc/asound/cardX/eld#0.0
Thanks a lot :)
--
Anssi Hannula
--
To unsubscribe from this list: send the line unsubscribe
c/asound/cardX/eld#0. I'd like to see the contents
>> both with radeon and with the proprietary fglrx driver in use
>>
> With fglrx 13.10 Beta 2:
>
> lano1106@whippet2 /proc/asound/card0 $ cat codec#0
Note I said eld#0, not codec#0 :)
Though I guess the correct filena
eld#0.0.
[...]
--
Anssi Hannula
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
02.10.2013 17:34, Takashi Iwai kirjoitti:
> At Tue, 1 Oct 2013 23:30:52 +0300,
> Anssi Hannula wrote:
[...]
>> Anssi Hannula (4):
>> ALSA: hda - hdmi: Add ATI/AMD multi-channel audio support
>> ALSA: hda - hdmi: Add ELD emulation for ATI/AMD codecs
>>
02.10.2013 17:34, Takashi Iwai kirjoitti:
At Tue, 1 Oct 2013 23:30:52 +0300,
Anssi Hannula wrote:
[...]
Anssi Hannula (4):
ALSA: hda - hdmi: Add ATI/AMD multi-channel audio support
ALSA: hda - hdmi: Add ELD emulation for ATI/AMD codecs
ALSA: hda - hdmi: Add HBR
/AMD_HDA_verbs_v2.pdf
Signed-off-by: Anssi Hannula
Tested-by: Peter Frühberger
---
sound/pci/hda/patch_hdmi.c | 65 +-
1 file changed, 64 insertions(+), 1 deletion(-)
diff --git a/sound/pci/hda/patch_hdmi.c b/sound/pci/hda/patch_hdmi.c
index 19adb01
for
providing more information than the previous revisions (but only if
supported by the display driver).
Generate ELD from the information provided by the vendor-specific verbs
on ATI/AMD codecs.
The specification is available at:
http://www.x.org/docs/AMD/AMD_HDA_verbs_v2.pdf
Signed-off-by: Anssi Hannula
parameters are marked as supported.
Support for multiple ports is also added to patch_atihdmi so that
0x1002aa01 codecs with multiple ports will work properly when switched
back to that patch.
Signed-off-by: Anssi Hannula
Tested-by: Peter Frühberger
---
sound/pci/hda/hda_local.h | 5 +
sound/pci
be found in combined form (for e.g. testing purposes) at:
http://onse.fi/files/atihdmi5.patch
The test file referenced above can be found at:
http://onse.fi/files/testi.dts.cut.spdif.gz (just regular DTS)
Anssi Hannula (4):
ALSA: hda - hdmi: Add ATI/AMD multi-channel audio support
ALSA
.
Apply the recommended values according to provided S/PDIF AES0 settings.
Signed-off-by: Anssi Hannula
---
sound/pci/hda/patch_hdmi.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/sound/pci/hda/patch_hdmi.c b/sound/pci/hda/patch_hdmi.c
index c0cd4ca..22f30fe 100644
--- a/sound
.
Apply the recommended values according to provided S/PDIF AES0 settings.
Signed-off-by: Anssi Hannula anssi.hann...@iki.fi
---
sound/pci/hda/patch_hdmi.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/sound/pci/hda/patch_hdmi.c b/sound/pci/hda/patch_hdmi.c
index c0cd4ca..22f30fe
be found in combined form (for e.g. testing purposes) at:
http://onse.fi/files/atihdmi5.patch
The test file referenced above can be found at:
http://onse.fi/files/testi.dts.cut.spdif.gz (just regular DTS)
Anssi Hannula (4):
ALSA: hda - hdmi: Add ATI/AMD multi-channel audio support
ALSA
parameters are marked as supported.
Support for multiple ports is also added to patch_atihdmi so that
0x1002aa01 codecs with multiple ports will work properly when switched
back to that patch.
Signed-off-by: Anssi Hannula anssi.hann...@iki.fi
Tested-by: Peter Frühberger frit...@xbmc.org
---
sound/pci
for
providing more information than the previous revisions (but only if
supported by the display driver).
Generate ELD from the information provided by the vendor-specific verbs
on ATI/AMD codecs.
The specification is available at:
http://www.x.org/docs/AMD/AMD_HDA_verbs_v2.pdf
Signed-off-by: Anssi Hannula
/AMD_HDA_verbs_v2.pdf
Signed-off-by: Anssi Hannula anssi.hann...@iki.fi
Tested-by: Peter Frühberger frit...@xbmc.org
---
sound/pci/hda/patch_hdmi.c | 65 +-
1 file changed, 64 insertions(+), 1 deletion(-)
diff --git a/sound/pci/hda/patch_hdmi.c b/sound/pci
of input devices
should be made compatible with both HAL and udev, with both
CONFIG_SYSFS_DEPRECATED and without it, as in 2.6.22 and before.
Is it possible to fall back to /class/input/inputX/eventY if SYSFS_DEPRECATED
is set?
Hopefully.
--
Anssi Hannula
-
To unsubscribe from this list: send
of input devices
should be made compatible with both HAL and udev, with both
CONFIG_SYSFS_DEPRECATED and without it, as in 2.6.22 and before.
Is it possible to fall back to /class/input/inputX/eventY if SYSFS_DEPRECATED
is set?
Hopefully.
--
Anssi Hannula
-
To unsubscribe from this list: send
v wrote:
On Sunday 09 September 2007 19:03, Kay Sievers wrote:
On 9/8/07, Anssi Hannula <[EMAIL PROTECTED]> wrote:
However, the change that broke id_path of udev is that
/sys/class/input/event5/device is now a symlink to the inputX directory
instead of being the same as the device syml
2007 19:03, Kay Sievers wrote:
On 9/8/07, Anssi Hannula [EMAIL PROTECTED] wrote:
However, the change that broke id_path of udev is that
/sys/class/input/event5/device is now a symlink to the inputX directory
instead of being the same as the device symlink in inputX directory,
i.e
Andrey Borzenkov wrote:
Anssi Hannula wrote:
Hi!
There seem to be changes in sysfs input structure between 2.6.22 and
2.6.23-rc5 which cause some breakage.
[...]
There is no longer:
/sys/class/input/eventX => /sys/class/input/inputX/eventX
instead there is:
/sys/class/inputX/input:eve
bly more time to adapt udev for coming changes in sysfs.
--
Anssi Hannula
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
.
--
Anssi Hannula
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Andrey Borzenkov wrote:
Anssi Hannula wrote:
Hi!
There seem to be changes in sysfs input structure between 2.6.22 and
2.6.23-rc5 which cause some breakage.
[...]
There is no longer:
/sys/class/input/eventX = /sys/class/input/inputX/eventX
instead there is:
/sys/class/inputX/input:eventX
ff-core.c or ff-memless.c.
(I also don't know what the triggers are useful for)
johann deneux also wrote in another message:
> The
> problem is to make an extension that does not duplicate the
> capabilities of the existing API. We don't want to have two ways of
> specifying the same e
not duplicate the
capabilities of the existing API. We don't want to have two ways of
specifying the same effects.
How is this a problem?
--
Anssi Hannula
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
d rather add
real effect types.
> Also yet another one such as FF_VECTOR or FF_3D could be considered as one
> posibility, but it's still the same -- to have no more than 3 entries to
> pass forces...
>
>> Do we have any idea if there any users of FF out there?
>
> At least m
and BZflag come to mind, though I think the support is quite
limited in both.
--
Anssi Hannula
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read
nt-
> E: ID_SERIAL=noserial
> E: ID_PATH=pci-1-1-
No ID_MODEL, ID_VENDOR, ID_REVISION, ID_TYPE etc etc.
Fix this by assigning the intf->dev into hid->dev, and fixing
all the users.
Signed-off-by: Anssi Hannula <[EMAIL PROTECTED]>
---
I recommend this fix to go to the stable tre
: ID_PATH=pci-1-1-
No ID_MODEL, ID_VENDOR, ID_REVISION, ID_TYPE etc etc.
Fix this by assigning the intf-dev into hid-dev, and fixing
all the users.
Signed-off-by: Anssi Hannula [EMAIL PROTECTED]
---
I recommend this fix to go to the stable tree before 2.6.20 is released.
diff -Nurp -x '*.mod' -x
These three patches fix PantherLord USB/PS2 2in1 Adapter support
so that it appears as two input devices, and add force feedback
support for it.
--
Anssi Hannula
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
Allow hid devices with HID_QUIRK_MULTI_INPUT to have force feedback.
This was previously disabled because there were not any force
feedback drivers for such devices. This will change with my upcoming
patch.
Signed-off-by: Anssi Hannula <[EMAIL PROTECTED]>
---
drivers/usb/input/hid-core.c
on 0810:0001, and allow the force feedback
driver to handle those.
Signed-off-by: Anssi Hannula <[EMAIL PROTECTED]>
---
drivers/hid/hid-input.c |6 +-
drivers/usb/input/hid-core.c |5 +
include/linux/hid.h |1 +
3 files changed, 11 insertions(+), 1 deletion(-)
Add a force feedback driver for PantherLord USB/PS2 2in1 Adapter,
0810:0001. The device identifies itself as "Twin USB Joystick".
Signed-off-by: Anssi Hannula <[EMAIL PROTECTED]>
---
drivers/usb/input/Kconfig|8 ++
drivers/usb/input/Makefile |3 +
drivers/us
Add a force feedback driver for PantherLord USB/PS2 2in1 Adapter,
0810:0001. The device identifies itself as Twin USB Joystick.
Signed-off-by: Anssi Hannula [EMAIL PROTECTED]
---
drivers/usb/input/Kconfig|8 ++
drivers/usb/input/Makefile |3 +
drivers/usb/input/hid-ff.c |3
on 0810:0001, and allow the force feedback
driver to handle those.
Signed-off-by: Anssi Hannula [EMAIL PROTECTED]
---
drivers/hid/hid-input.c |6 +-
drivers/usb/input/hid-core.c |5 +
include/linux/hid.h |1 +
3 files changed, 11 insertions(+), 1 deletion(-)
Index
Allow hid devices with HID_QUIRK_MULTI_INPUT to have force feedback.
This was previously disabled because there were not any force
feedback drivers for such devices. This will change with my upcoming
patch.
Signed-off-by: Anssi Hannula [EMAIL PROTECTED]
---
drivers/usb/input/hid-core.c |6
These three patches fix PantherLord USB/PS2 2in1 Adapter support
so that it appears as two input devices, and add force feedback
support for it.
--
Anssi Hannula
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo
PRE_FAIL".
But this is; Reallocated sector count above zero indicates a failing
harddrive.
More information here:
http://smartmontools.sourceforge.net/BadBlockHowTo.txt
If the count is "very high", I think you should get a new harddrive.
--
Anssi Hannula
-
To unsubscribe from this list: sen
.
But this is; Reallocated sector count above zero indicates a failing
harddrive.
More information here:
http://smartmontools.sourceforge.net/BadBlockHowTo.txt
If the count is very high, I think you should get a new harddrive.
--
Anssi Hannula
-
To unsubscribe from this list: send the line unsubscribe linux
Vojtech Pavlik wrote:
On Thu, Jul 07, 2005 at 05:20:59PM +0300, Anssi Hannula wrote:
But I think we should not apply (with or without 64-bit) the patch (not
yet, anyway), as I'm (slowly) working on restructuring the kernel FF
interface and developing a user space library (and writing
Vojtech Pavlik wrote:
On Thu, Jul 07, 2005 at 05:20:59PM +0300, Anssi Hannula wrote:
But I think we should not apply (with or without 64-bit) the patch (not
yet, anyway), as I'm (slowly) working on restructuring the kernel FF
interface and developing a user space library (and writing
Vojtech Pavlik wrote:
On Fri, Apr 08, 2005 at 08:29:52PM +0300, Anssi Hannula wrote:
This patch adds Force Feedback interface to joydev. I felt this
necessary because games usually don't run as root while evdev usually
can't be read or written by anyone else. Patch is against 2.6.12-rc2
Vojtech Pavlik wrote:
On Fri, Apr 08, 2005 at 08:29:52PM +0300, Anssi Hannula wrote:
This patch adds Force Feedback interface to joydev. I felt this
necessary because games usually don't run as root while evdev usually
can't be read or written by anyone else. Patch is against 2.6.12-rc2
have enough time and skills, I will start developing userspace
Force Feedback library, which would do (among other things) all
necessary force convertings between joystick, gamepad and wheel controllers.
Does anyone have any thoughts about this?
Signed-off-by: Anssi Hannula <[EMAIL PROTEC
have enough time and skills, I will start developing userspace
Force Feedback library, which would do (among other things) all
necessary force convertings between joystick, gamepad and wheel controllers.
Does anyone have any thoughts about this?
Signed-off-by: Anssi Hannula [EMAIL PROTECTED]
diff
elp on one system, so I'm 50%
better off - just need to find out where to put the command so that it loads
it on startup...modules.conf would be it I guess.
Put it on /etc/modprobe.preload
--
Anssi Hannula
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
system, so I'm 50%
better off - just need to find out where to put the command so that it loads
it on startup...modules.conf would be it I guess.
Put it on /etc/modprobe.preload
--
Anssi Hannula
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
73 matches
Mail list logo
