All of lore.kernel.org
 help / color / mirror / Atom feed
From: TAXI <taxi@a-city.de>
To: BOUWSMA Barry <freebeer.bouwsma@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Bad image/sound quality with Medion MD 95700
Date: Fri, 25 Dec 2009 11:38:21 +0100	[thread overview]
Message-ID: <4B34961D.6060207@a-city.de> (raw)
In-Reply-To: <alpine.DEB.2.01.0912251021210.5481@ybpnyubfg.ybpnyqbznva>

BOUWSMA Barry schrieb:
> The other thing to note is that this device delivers a full
> unfiltered Transport Stream, which with the 13,27Mbit/sec typical
> bandwidth per channel used in your country (apart from some local
> exceptions of greater values), will require a USB2 interface.
it is a USB2 interface:
[    3.965425] usb 1-3.1: new high speed USB device using ehci_hcd and
address 6 (it's the USB hub in the box)

I also thought the USB chipset could be the problem and testet it with
an extra USB2 card.

> around line 620 in my reference code, there is a line that sets
> the alternate interface to 6.  This is expected to be bulk, but
> on my boxes is isoc.
> 
> You can change this to interface 0, on which my boxes delivers
> bulk data flawlessly.
I think isoc would be okay on 2.6.32, so no need to change that, right?

> but when
> I have my machine operating fully again (yeahright), I can send
> you some of these alternative patches to try -- running 
> successfully on 2.6.14 and 2.6.27-rc4.
That would be nice.

P.S. my english is not the best so I don't understand all you wrote but
why don't you put the patches upstream?

  reply	other threads:[~2009-12-25 10:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-24 23:10 Bad image/sound quality with Medion MD 95700 TAXI
2009-12-25  9:51 ` BOUWSMA Barry
2009-12-25 10:38   ` TAXI [this message]
2009-12-25 12:29     ` BOUWSMA Barry
2009-12-25 15:35     ` BOUWSMA Barry
2009-12-25 15:50       ` TAXI
2009-12-25 16:13         ` BOUWSMA Barry
  -- strict thread matches above, loose matches on Subject: below --
2009-12-25 13:15 TAXI

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B34961D.6060207@a-city.de \
    --to=taxi@a-city.de \
    --cc=freebeer.bouwsma@gmail.com \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.