A split for ds3000/ts2020 code forgot to change the TEVII_S471 code.
Change the TEVII_S471 according the changes to TEVII_S470.
Signed-off-by: Christian Volkmann
---
drivers/media/pci/cx23885/cx23885-dvb.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/media
A split for ds3000/ts2020 code forgot to change the TEVII_S471 code.
Change the TEVII_S471 according the changes to TEVII_S470.
Signed-off-by: Christian Volkmann c...@cv-sv.de
---
drivers/media/pci/cx23885/cx23885-dvb.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
Pete Zaitcev wrote:
> On Sat, 15 Sep 2007 03:48:19 -0700, Andrew Morton <[EMAIL PROTECTED]> wrote:
>
>>> I have an error message with 2.6.23-rc6.
>>> This did not happen with 2.6.22.
>> Another one for Michal's dirt file.
>
> No, I think it's the module ordering again.
>
>>> 2.6.23-rc6 boot.msg
pting address 2, error -62
and nothing is harmed.
Andrew Morton wrote:
> Let's cc the USB mailing list.
>
> On Fri, 14 Sep 2007 23:28:23 +0200 Christian Volkmann <[EMAIL PROTECTED]>
> wrote:
>
>> Hi everybody,
>>
>> I have an error message with 2.6.2
ror -62
and nothing is harmed.
Andrew Morton wrote:
> Let's cc the USB mailing list.
>
> On Fri, 14 Sep 2007 23:28:23 +0200 Christian Volkmann <[EMAIL PROTECTED]>
> wrote:
>
>> Hi everybody,
>>
>> I have an error message with 2.6.23-rc6.
>&g
Morton wrote:
Let's cc the USB mailing list.
On Fri, 14 Sep 2007 23:28:23 +0200 Christian Volkmann [EMAIL PROTECTED]
wrote:
Hi everybody,
I have an error message with 2.6.23-rc6.
This did not happen with 2.6.22.
Another one for Michal's dirt file.
The kernel reports message like
.
On Fri, 14 Sep 2007 23:28:23 +0200 Christian Volkmann [EMAIL PROTECTED]
wrote:
Hi everybody,
I have an error message with 2.6.23-rc6.
This did not happen with 2.6.22.
Another one for Michal's dirt file.
The kernel reports message like this:
3usb 1-1: device not accepting address 2
Pete Zaitcev wrote:
On Sat, 15 Sep 2007 03:48:19 -0700, Andrew Morton [EMAIL PROTECTED] wrote:
I have an error message with 2.6.23-rc6.
This did not happen with 2.6.22.
Another one for Michal's dirt file.
No, I think it's the module ordering again.
2.6.23-rc6 boot.msg extract ( hub/usb
Hi everybody,
I have an error message with 2.6.23-rc6.
This did not happen with 2.6.22.
The kernel reports message like this:
<3>usb 1-1: device not accepting address 2, error -62
<3>hub 2-2.1:1.0: hub_port_status failed (err = -71)
Does this message harm or is something broken in 2.6.23-rc6
Hi everybody,
I have an error message with 2.6.23-rc6.
This did not happen with 2.6.22.
The kernel reports message like this:
3usb 1-1: device not accepting address 2, error -62
3hub 2-2.1:1.0: hub_port_status failed (err = -71)
Does this message harm or is something broken in 2.6.23-rc6 ?
I
A bug report is at https://bugzilla.samba.org/show_bug.cgi?id=4819
-
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
A bug report is at https://bugzilla.samba.org/show_bug.cgi?id=4819
-
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
Hi,
I had several Oops in messages.
The kernel 2.6.22 is tainted with a vmware module.
Please ignore this mail if you expect vmware-modules had crashed the system.
The vmware had not been used during the uptime.
But may be somebody can find some errors also with a tainted kernel.
I will try to
Hi,
I had several Oops in messages.
The kernel 2.6.22 is tainted with a vmware module.
Please ignore this mail if you expect vmware-modules had crashed the system.
The vmware had not been used during the uptime.
But may be somebody can find some errors also with a tainted kernel.
I will try to
Thu, May 17, 2007 at 05:47:54PM -0400, Dave Jones wrote:
> > > On Thu, May 17, 2007 at 11:28:01PM +0200, Christian Volkmann wrote:
> > >
> > > > - Important: somebody to check other CPU types if the same behavior
> happens.
> > >
> > > ar
, 2007 at 05:47:54PM -0400, Dave Jones wrote:
On Thu, May 17, 2007 at 11:28:01PM +0200, Christian Volkmann wrote:
- Important: somebody to check other CPU types if the same behavior
happens.
arch/i386/kernel/cpu/rise.c
Though, I've *never* seen or even heard
Claas Langbehn wrote:
> Could anyone explain to me what CMPXCHG64 / cx8 is and what happens if
> the kernel has been compiled to use it but the CPU does not have it?
>
> Regards,
> claas
>
Hi Claas,
the bug is at another place. But it's hidden if X86_CMPXCHG64 is
switched of.
There are 3
Claas Langbehn wrote:
Could anyone explain to me what CMPXCHG64 / cx8 is and what happens if
the kernel has been compiled to use it but the CPU does not have it?
Regards,
claas
Hi Claas,
the bug is at another place. But it's hidden if X86_CMPXCHG64 is
switched of.
There are 3 errors.
it... when enabled it shows up.
PS: @Simon, sorry that I missed the other thread. Too much traffic
and not enough time for me to read all. I suppose that's a fulltime job ;-)
Claas Langbehn wrote:
> Simon Arlott schrieb:
>> On 19/05/07 23:36, Christian Volkmann wrote:
>>> Christian
missed the other thread. Too much traffic
and not enough time for me to read all. I suppose that's a fulltime job ;-)
Claas Langbehn wrote:
Simon Arlott schrieb:
On 19/05/07 23:36, Christian Volkmann wrote:
Christian Volkmann wrote:
Claas asked for the NX flag for the Via C3 (?) processors
Christian Volkmann wrote:
> Hi,
>
> Claas asked for the NX flag for the Via C3 (?) processors
> in another thread.
>
> I do not know another synonym for this?
>
> Claas Langbehn wrote:
>> Hello Christian,
>>
>> do you know if and how it's possible to e
Hi,
Claas asked for the NX flag for the Via C3 (?) processors
in another thread.
I do not know another synonym for this?
Claas Langbehn wrote:
> Hello Christian,
>
> do you know if and how it's possible to enable NX_bit too?
>
>
> Claas
>
The via C3 documentation is at:
Andi Kleen wrote:
> Can someone please test if this patch works?
>
> This preserves the 6 <= model <= 9 logic of the C code; this means
> if VIA ever brings out model >= 10 it hopefully sets this bit by default.
> Dave, do you have any information to the contrary?
>
> -Andi
>
Hi Andi,
your
Andi Kleen wrote:
Can someone please test if this patch works?
This preserves the 6 = model = 9 logic of the C code; this means
if VIA ever brings out model = 10 it hopefully sets this bit by default.
Dave, do you have any information to the contrary?
-Andi
Hi Andi,
your patch did
Hi,
Claas asked for the NX flag for the Via C3 (?) processors
in another thread.
I do not know another synonym for this?
Claas Langbehn wrote:
Hello Christian,
do you know if and how it's possible to enable NX_bit too?
Claas
The via C3 documentation is at:
Christian Volkmann wrote:
Hi,
Claas asked for the NX flag for the Via C3 (?) processors
in another thread.
I do not know another synonym for this?
Claas Langbehn wrote:
Hello Christian,
do you know if and how it's possible to enable NX_bit too?
Claas
C7 Esther:
Hmm, I expect
Dave Jones wrote:
> On Thu, May 17, 2007 at 11:28:01PM +0200, Christian Volkmann wrote:
> Though, I've *never* seen or even heard of someone with one of those CPUs,
> so whether we need to care is questionable. The mp6 did actually make it
> to manufacture aparently, but I don't
Christian wrote:
Hmm, I really think so...:
>
> May I brought up a wrong reason with the command cmpxchg64.
> But disabling CONFIG_X86_CMPXCHG64 helps.
>
Hi,
I found some time to investigate. My resume is:
- kernel/verify_cpu.S causes the stop at boot time
Cause the required flag for
Christian wrote:
Hmm, I really think so...:
May I brought up a wrong reason with the command cmpxchg64.
But disabling CONFIG_X86_CMPXCHG64 helps.
Hi,
I found some time to investigate. My resume is:
- kernel/verify_cpu.S causes the stop at boot time
Cause the required flag for
Dave Jones wrote:
On Thu, May 17, 2007 at 11:28:01PM +0200, Christian Volkmann wrote:
Though, I've *never* seen or even heard of someone with one of those CPUs,
so whether we need to care is questionable. The mp6 did actually make it
to manufacture aparently, but I don't think anyone actually
30 matches
Mail list logo
