The GET_REVISION command puts the device in an unresponsive state,
although it continues to report any IR activity. Note that GET_REVISION
command is not documented, nor is any possible response to it parsed.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/mceusb.c | 8 +++-
1
spotted by sparse.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/ttusbir.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/media/rc/ttusbir.c b/drivers/media/rc/ttusbir.c
index f9226b8..cf0d47f 100644
--- a/drivers/media/rc/ttusbir.c
+++ b
If more than 127 different lengths are transmitted then the driver causes
an overrun on sample_lens. Try to send as much as possible and return the
amount sent.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/redrat3.c | 18 ++
1 file changed, 6 insertions(+), 12
On cold boot the device does not initialize until the first packet is
received, and that packet is not processed.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/iguanair.c | 25 +++--
1 file changed, 15 insertions(+), 10 deletions(-)
diff --git a/drivers/media
On Sun, Jan 06, 2013 at 05:19:45PM +, Sean Young wrote:
Sometimes the first version request is sent before the device has fully
initialized. This seems to happen on some hardware during boot when the
iguanair is plugged into a root hub.
Signed-off-by: Sean Young s...@mess.org
Mauro
On Fri, Jan 11, 2013 at 5:35 AM, Leela Krishna Amudala
l.kris...@samsung.com wrote:
The Exynos DP transmitter is treated as an end entity in the display pipeline
and made this RFC patch compliant with CDF.
Any suggestions are welcome.
A few comments below. It's hard to get too much of an
A sample resolution of 2us generates more than 300 interrupts per key
and this resolution is not needed unless carrier reports are enabled.
Revert to a resolution of 10us unless carrier reports are needed. This
generates up to a fifth of the interrupts.
Signed-off-by: Sean Young s...@mess.org
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/iguanair.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/rc/iguanair.c b/drivers/media/rc/iguanair.c
index 5a9163d..a569c69 100644
--- a/drivers/media/rc/iguanair.c
+++ b/drivers/media/rc/iguanair.c
@@ -512,6 +512,7
Sometimes the first version request is sent before the device has fully
initialized. This seems to happen on some hardware during boot when the
iguanair is plugged into a root hub.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/iguanair.c | 19 ++-
1 file changed
On Thu, Jan 03, 2013 at 01:16:57AM +0100, David Härdeman wrote:
On Wed, Oct 24, 2012 at 10:22:41PM +0100, Sean Young wrote:
This is needed for carrier reporting.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/winbond-cir.c | 14 +-
1 file changed, 9 insertions
Signed-off-by: Sean Young s...@mess.org
---
MAINTAINERS | 12
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index f4b3aa8..1a69d21 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3751,6 +3751,12 @@ F: net/ieee802154/
F: net
The receiver is never disabled by idle mode since rxstate never gets set
to RXSTATE_ACTIVE, so we keep on getting interrupts after the first IR
activity ends. Note that ir_raw_event_reset() already calls
ir_raw_event_handle().
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/winbond
This is needed for carrier reporting.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/winbond-cir.c | 14 +-
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/drivers/media/rc/winbond-cir.c b/drivers/media/rc/winbond-cir.c
index 6f0f5ef..1ff47eb 100644
The winbond hardware has a counter for leading edges, which increases as
they are received. As we read raw IR from a fifo in an interrupt handler,
we cannot correlate them to specific IR pulses so we simply count all
pulses and edges until we go idle and disable the receiver.
Signed-off-by: Sean
On Thu, Oct 18, 2012 at 11:59:21PM +0200, David Härdeman wrote:
On Wed, Oct 17, 2012 at 05:18:56PM +0100, Sean Young wrote:
On Fri, Oct 12, 2012 at 01:11:54AM +0200, David Härdeman wrote:
The RC_TYPE_* defines are currently used both where a single protocol is
expected and where a bitmap
54fd321 [media] winbond: remove space from driver name inadvertently
renamed the input device name.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/winbond-cir.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/media/rc/winbond-cir.c b/drivers/media/rc
On Fri, Oct 12, 2012 at 01:16:36AM +0200, David Härdeman wrote:
On Fri, Sep 28, 2012 at 09:44:33AM +0100, Sean Young wrote:
[root@pequod ~]# udevadm test /sys/class/rc/rc0
-snip-
ACTION=add
DEVPATH=/devices/pnp0/00:04/rc/rc0
DRV_NAME=Winbond CIR
NAME=rc-rc6-mce
SUBSYSTEM=rc
UDEV_LOG=6
Note that the firmware already disables the receiver before transmit,
there is no need to do this from the driver.
Reported-by: Fengguang Wu fengguang...@intel.com
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/iguanair.c | 147 ++--
1 file
/rc_maps.cfg.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/winbond-cir.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/rc/winbond-cir.c b/drivers/media/rc/winbond-cir.c
index 30ae1f2..7c9b5f3 100644
--- a/drivers/media/rc/winbond-cir.c
+++ b/drivers
together so I don't know
when I or anyone else will have this finished.
Sean
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
means disabling carrier modulation, which is used by
the mceusb driver.
So the check belongs in the individual drivers, as in the original patch.
Sean
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo
to different evnets since their protocol is
different?
At the moment, no. David Hardeman has sent a patch for this:
http://patchwork.linuxtv.org/patch/11388/
Sean
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More
On Mon, Sep 03, 2012 at 11:41:55PM +0200, David Härdeman wrote:
Hej,
On Mon, Sep 03, 2012 at 01:36:53PM +0100, Sean Young wrote:
On Sun, Sep 02, 2012 at 11:08:20PM +0300, Timo Kokkonen wrote:
I guess the assumption is to avoid
breaking the transmission in the middle in case the process
safety measure that this driver behaves well.
In that case I think you should use wait_event_interruptible() instead.
Well, that's what I had there in the first place. With interruptible
wait we are left with problem with signals. I was told by Sean Young
that the lirc API expects
On Sat, Sep 01, 2012 at 09:57:09AM +0800, Du, Changbin wrote:
From: Du, Changbin changbin...@gmail.com
Each rc-raw device has a property allowed_protos stored in structure
ir_raw_event_ctrl. But it didn't work because all decoders would be
called when decoding. This path makes only allowed
The led is green, not yellow.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/ttusbir.c | 48 ++
1 file changed, 44 insertions(+), 4 deletions(-)
diff --git a/drivers/media/rc/ttusbir.c b/drivers/media/rc/ttusbir.c
index 2151927..f0921b5
On Sat, Aug 25, 2012 at 11:25:26AM +0200, David Härdeman wrote:
On Sat, Aug 25, 2012 at 12:26:25AM +0100, Sean Young wrote:
On Sat, Aug 25, 2012 at 12:05:18AM +0200, David Härdeman wrote:
On Thu, Aug 23, 2012 at 10:18:35PM +0100, Sean Young wrote:
Some drivers wait for the IR device
Since commit [media] rc-core: move timeout and checks to lirc, the
incoming buffer is used after the driver transmits.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/iguanair.c | 51 +++--
1 file changed, 21 insertions(+), 30 deletions
On Wed, Aug 22, 2012 at 10:50:35PM +0300, Timo Kokkonen wrote:
The lirc-dev expects the ir-code to be transmitted when the write call
returns back to the user space. We should not leave TX ongoing no
matter what is the reason we return to the user space. Easiest
solution for that is to simply
On Sat, Aug 25, 2012 at 12:16:04AM +0200, David Härdeman wrote:
On Thu, Aug 16, 2012 at 11:15:14PM +0100, Sean Young wrote:
The lirc TX functionality expects the process which writes (TX) data to
the lirc dev to sleep until the actual data has been transmitted by the
hardware.
Since
On Sat, Aug 25, 2012 at 12:05:18AM +0200, David Härdeman wrote:
On Thu, Aug 23, 2012 at 10:18:35PM +0100, Sean Young wrote:
Some drivers wait for the IR device to complete sending before
returning, so sleeping should not be done.
I'm not quite sure what the purpose is. Even if a driver waits
[media] rc-core: move timeout and checks to lirc introduced a buffer
overrun by passing the number of bytes, rather than the number of samples,
to the transmit function.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/ir-lirc-codec.c | 2 +-
1 file changed, 1 insertion(+), 1
This patch fixes the error:
ERROR: usb_speed_string [drivers/usb/core/usbcore.ko] undefined!
Reported-by: Guenter Roeck li...@roeck-us.net
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/media/rc/Kconfig b/drivers
On Mon, Aug 20, 2012 at 07:02:47PM -0300, Mauro Carvalho Chehab wrote:
Em 20-08-2012 18:36, David Härdeman escreveu:
On Thu, Aug 16, 2012 at 08:12:34PM -0300, Mauro Carvalho Chehab wrote:
Em 16-08-2012 19:15, Sean Young escreveu:
Could we have a flag in rc_dev to signify whether a driver
On Thu, Aug 16, 2012 at 09:19:09AM -0700, Greg KH wrote:
On Tue, Jul 31, 2012 at 11:37:03AM +0100, Sean Young wrote:
The serial driver will detect the winbond cir device as a serial port,
since it looks exactly like a serial port unless you know what it is
from the PNP ID.
Winbond CIR
(total_duration));
return count;
}
--
1.7.11.2
Sean
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Fri, Aug 10, 2012 at 11:41:23PM +0600, Partha Guha Roy wrote:
On Fri, Aug 10, 2012 at 3:47 PM, Sean Young s...@mess.org wrote:
Are you runnning the lircd user space process for input or relying on
the in-kernel decoders?
For my testing, I booted the vanilla kernel into ubuntu recovery
Rather than using usb_interrupt_msg() to receive responses, reuse the
urb callback we already have in place.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/iguanair.c | 147 +---
1 file changed, 56 insertions(+), 91 deletions(-)
diff --git
Firmware versions lower than 0x0205 use a different interface which is not
supported. Also report the firmware version in the standard format.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/Kconfig| 8 ++--
drivers/media/rc/iguanair.c | 21 +++--
2 files
Now unbind also stops the receiver.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/iguanair.c | 21 ++---
1 file changed, 14 insertions(+), 7 deletions(-)
diff --git a/drivers/media/rc/iguanair.c b/drivers/media/rc/iguanair.c
index 4525107..a6a19eb 100644
Also fix error codes returned from open.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/iguanair.c | 30 ++
1 file changed, 18 insertions(+), 12 deletions(-)
diff --git a/drivers/media/rc/iguanair.c b/drivers/media/rc/iguanair.c
index 7eeabdb..4525107
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/iguanair.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/media/rc/iguanair.c b/drivers/media/rc/iguanair.c
index a6a19eb..9810008 100644
--- a/drivers/media/rc/iguanair.c
+++ b/drivers/media/rc/iguanair.c
@@ -124,6
This has been replaced by the ttusbir driver.
Signed-off-by: Sean Young s...@mess.org
---
drivers/staging/media/lirc/Kconfig| 6 -
drivers/staging/media/lirc/Makefile | 1 -
drivers/staging/media/lirc/lirc_ttusbir.c | 376 --
3 files changed, 383
There is a proper ene0100 driver anyway.
Signed-off-by: Sean Young s...@mess.org
---
drivers/staging/media/lirc/lirc_ene0100.h | 169 --
1 file changed, 169 deletions(-)
delete mode 100644 drivers/staging/media/lirc/lirc_ene0100.h
diff --git a/drivers/staging/media
handle at most
700 edges per second. The remote generates about 900.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/iguanair.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/media/rc/iguanair.c b/drivers/media/rc/iguanair.c
index 9810008..6a09c2e
With the timeout supplied the interface can go idle. The keymap is
the same one as other drivers which do not come with a remote.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/iguanair.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/media/rc
This driver adds support for TechnoTrend USB IR Receiver. It is a complete
rewrite of the staging/media/lirc/lirc_ttusbir driver. It adds more
accurate sample reporting and led control.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/Kconfig | 13 ++
drivers/media/rc
The TechnoTrend USB IR Receiver sends 125 ISO URBs per second, even when
there is no IR activity. Reduce the number of wake ups from the other
drivers too.
This saves about 0.25ms/s on a 2.4GHz Core 2 according to powertop.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/fintek
tested only.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/video/saa7134/saa7134-input.c | 10 +++---
drivers/media/video/saa7134/saa7134.h | 1 -
2 files changed, 3 insertions(+), 8 deletions(-)
diff --git a/drivers/media/video/saa7134/saa7134-input.c
b/drivers/media/video
Currently write() will return 0 if an IR device does not support sending.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/ir-lirc-codec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/rc/ir-lirc-codec.c b/drivers/media/rc/ir-lirc-codec.c
index
On Fri, Aug 10, 2012 at 01:16:36PM +0300, Timo Kokkonen wrote:
This is the driver for the IR transmitter diode found on the Nokia
N900 (also known as RX51) device. The driver is mostly the same as
found in the original 2.6.28 based kernel that comes with the device.
The following
On Sat, Aug 11, 2012 at 09:35:29PM -0300, Mauro Carvalho Chehab wrote:
Em 31-07-2012 07:37, Sean Young escreveu:
This fixes:
- rx_overflow while holding down any down button on a nec remote
- suspend/resume
- stop receiver on rmmod
- advertise rx_resolution and timeout properly
On Fri, Aug 10, 2012 at 08:28:03PM +0100, Sean Young wrote:
Transmit returned 0 after sending and failed to send anything if the amount
exceeded its buffer size. Also fix some minor errors.
Signed-off-by: Sean Young s...@mess.org
I'm sorry, this patch series wasn't diffed against the right
be surprised if the 15ms delay for processing in
saa7134_raw_decode_irq (bottom of saa7134-input.c) needs increasing.
Sean
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
Currently write() will return 0 if an IR device does not support sending.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/ir-lirc-codec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/media/rc/ir-lirc-codec.c b/drivers/media/rc/ir-lirc-codec.c
index
We now have a proper driver which uses rc-core.
Signed-off-by: Sean Young s...@mess.org
---
drivers/staging/media/lirc/Kconfig| 6 -
drivers/staging/media/lirc/Makefile | 1 -
drivers/staging/media/lirc/lirc_ttusbir.c | 376 --
3 files changed, 383
The TechnoTrend USB IR Receiver sends 125 ISO URBs per second, even when
there is no IR activity. Reduce the number of wake ups from the other
drivers too.
This saves about 0.25ms per second on a 2.4GHz Core 2 according to
powertop.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc
This driver is loosely based on the lirc_ttusbir driver in the staging area,
but adds more accurate sampling and led control.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/Kconfig | 13 ++
drivers/media/rc/Makefile | 1 +
drivers/media/rc/keymaps/rc-tt
There is a proper ene0100 driver anyway.
Signed-off-by: Sean Young s...@mess.org
---
drivers/staging/media/lirc/lirc_ene0100.h | 169 --
1 file changed, 169 deletions(-)
delete mode 100644 drivers/staging/media/lirc/lirc_ene0100.h
diff --git a/drivers/staging/media
-off-by: Sean Young s...@mess.org
---
drivers/media/rc/winbond-cir.c | 21 -
drivers/tty/serial/8250/8250.c | 1 +
2 files changed, 21 insertions(+), 1 deletion(-)
diff --git a/drivers/media/rc/winbond-cir.c b/drivers/media/rc/winbond-cir.c
index 54ee348..20a0bbb 100644
This remote sends a header pulse of 8150us followed by a space of 4000us.
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/ir-nec-decoder.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/media/rc/ir-nec-decoder.c
b/drivers/media/rc/ir-nec-decoder.c
This fixes:
- rx_overflow while holding down any down button on a nec remote
- suspend/resume
- stop receiver on rmmod
- advertise rx_resolution and timeout properly
- code simplify
- ignore unsupported firmware versions
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/Kconfig
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/mceusb.c | 13 +
1 files changed, 5 insertions(+), 8 deletions(-)
diff --git a/drivers/media/rc/mceusb.c b/drivers/media/rc/mceusb.c
index e150a2e..1af0b0c 100644
--- a/drivers/media/rc/mceusb.c
+++ b/drivers/media/rc
Signed-off-by: Sean Young s...@mess.org
---
drivers/media/rc/Kconfig| 11 +
drivers/media/rc/Makefile |1 +
drivers/media/rc/iguanair.c | 639 +++
3 files changed, 651 insertions(+), 0 deletions(-)
create mode 100644 drivers/media/rc
on input which also has dependants.
This can save a reasonable amount of memory:
$ ./scripts/bloat-o-meter vmlinux vmlinux-no-rc add/remove: 0/909 grow/shrink:
1/20 up/down: 4/-159171 (-159167)
Diff against current mainline.
Signed-off-by: Sean Young s...@mess.org
---
diff --git a/drivers/media
as in Windows.
Tested on an AverMedia GO 007 FM Plus.
Signed-off-by: Sean Young s...@mess.org
--
diff --git a/drivers/media/video/saa7134/saa7134-video.c
b/drivers/media/video/saa7134/saa7134-video.c
index cb73264..31138d3 100644
--- a/drivers/media/video/saa7134/saa7134-video.c
+++ b/drivers/media
What kind of errors or problems are you getting?
Can you turn on debugging and give us some output?
Sean
--Original Message--
From: sacarde
Sender: linux-media-ow...@vger.kernel.org
To: linux-media@vger.kernel.org
Subject: problem webcam gspca 2.6.32
Sent: Jan 9, 2010 12:32 AM
hi
;
+ }
+
td-ed-hwTailP = td-hwNextTD;
}
Alan,
This last patch seems to do the job. Thanks so much for your help! Where
do I donate/send beer?
Sean
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
||moin...@free.fr
--- Comment #22 from Jean-Francois Moine moin...@free.fr 2010-01-03 07:02:45
---
Hello Sean,
Sorry to be a bit late. Looking at the dmesg, I found that the gspca version
was 2.7.0. May you upgrade your linux media stuff from LinuxTv.org and check
Alan Stern wrote:
Um, when you say it does the job, what do you mean?
It traps the error and prevents the kernel from crashing.
The job it was _intended_ to do was to prove that your problems are
caused by hardware errors rather than software bugs. If the patch
causes the problems to stop,
to
remove the camera. Attached are the serial console capture as well as
the dmesg log in debug4.tar.gz. Did you want me to try to reproduce the
poison message?
Sean
debug4.tar.gz
Description: Unix tar archive
Alan,
Thanks again. I was able to get the full dmesg output this time. I ran
capture-example three times and each time removing the webcam before
capture-example finished. On the third time I got the poisoned hash
message and I captured the output to a file. Attached is the dmesg output.
Sean
a hardware memory error. What do you think?
Attached is the latest dmesg output.
Sean
dmesg3.log.tar.gz
Description: Unix tar archive
return in td_free that is in the patch will trap the error.
I changed the debug statements to ohci_dbg and I was able to capture
the full output with klogd. It is attached.
Sean
Sean wrote:
In looking at the log file it seems that there is a mismatch of td_alloc
calls and td_free calls
.
That's because you didn't get the full output. Here's an enhanced
version of the patch. It will provide more information and perhaps a
smoking gun.
Alan Stern
Alan,
Thanks for the debug patch. I'll send you the dmesg.log output in
another email. It is 2MB.
Sean
--
To unsubscribe
Sean Lazar
--- ohci-mem.c.orig2009-12-16 22:57:49.0 +
+++ ohci-mem.c2009-12-16 22:49:37.0 +
@@ -103,8 +103,13 @@
{
struct td**prev = hc-td_hash [TD_HASH_FUNC (td-td_dma)];
-while (*prev *prev != td)
+while (*prev *prev != td
Is there anything I can do to help? This is a show stopping bug for me.
Thanks,
Sean Lazar
Alan Stern wrote:
On Wed, 11 Nov 2009, Andrew Morton wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=14564
Summary: capture-example sleeping function called from invalid
and libv4l2 from mercurial. http://linuxtv.org/hg/v4l-dvb
Sean
bifferos wrote:
Hi all,
Can anyone give any clue as to why I might get this error
when capturing from a PAC207 webcam? It happens after a 6-7
second delay when capturing.
I've seen this with 2.6.30.1, 2.6.30.5 and 2.6.32-rc7, however
I
Thanks for your reply.
That makes a lot of sense, because this is an embedded platform and
there is no swap! But there seems to be 89544K free while
capture-example is running. hmmm.
Sean Lazar
Hans de Goede wrote:
Hi,
On 11/04/2009 10:37 AM, Sean wrote:
Hi, I am having a bug when
I'm still having trouble with capture-example.c completely locking up my
system. The same os image on other hardware works fine. Where do I start
looking? What can I do to debug this issue?
Sean
Sean wrote:
Hi,
I have compiled kernel 2.6.30 from kernel.org, and I have also
compiled capture
1001 - 1080 of 1080 matches
Mail list logo
