From: "Daniel Glöckner" <daniel-gl@gmx.net>
To: Jean Delvare <jdelvare@suse.de>
Cc: v4l-dvb maintainer list <v4l-dvb-maintainer@linuxtv.org>,
Linux and Kernel Video <video4linux-list@redhat.com>,
Trent Piepho <xyzzy@speakeasy.org>
Subject: Re: bttv driver questions
Date: Sat, 30 Aug 2008 18:44:44 +0200 [thread overview]
Message-ID: <20080830164444.GA263@daniel.bse> (raw)
In-Reply-To: <200808300954.19361.jdelvare@suse.de>
On Sat, Aug 30, 2008 at 09:54:18AM +0200, Jean Delvare wrote:
> But I have to admit that I'm not really sure how the different PCI
> Express slots relate to each other. Does each slot have its own bus
> and thus bandwidth? Or is the same PCI Express bus shared by all
> slots as is usually the case for PCI?
Each slot has the full bandwidth, but the receiving end can stop the
transmitter if it has no space left in its buffer.
> And what about the motherboards
> which have both PCI and PCI Express slots/on-board devices?
There will be a PCI-PCIe bridge. Both busses will be independent as
long as they don't exchange data.
> I see no reference to the XIO2000 in the kernel source tree. If I am
> supposed to tweak QoS parameters, how would I do that?
Having read the XIO2000 datasheet I would try to use the second VC with
a higher traffic class for access from the PCI bus to memory.
The configuration of the bridge should be modifiable with setpci.
Other chips might need tweaking too for this to have effect.
> According to "lspci -vv" the latency timer of the bridge is set to 0.
The latency timer is meaningless for PCIe.
The secondary, PCI bus has a separate latency timer, but I wouldn't set
that one to a high value.
> As far as I remember, all PCI-PCI bridges I've ever seen always had
> their latency timer set to 0.
0 is the default for a bridge after reset.
Daniel
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
prev parent reply other threads:[~2008-08-30 16:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200808251445.22005.jdelvare@suse.de>
2008-08-26 0:40 ` [v4l-dvb-maintainer] bttv driver questions Andy Walls
2008-08-26 23:29 ` Daniel Glöckner
2008-08-27 2:20 ` Trent Piepho
2008-08-27 2:59 ` Robert William Fuller
2008-08-28 19:43 ` Trent Piepho
2008-08-27 3:45 ` Andy Walls
2008-08-28 19:48 ` Trent Piepho
[not found] ` <200808281611.38241.jdelvare@suse.de>
2008-08-28 20:20 ` Daniel Glöckner
2008-08-28 21:42 ` hermann pitton
[not found] ` <200808301201.47561.jdelvare@suse.de>
2008-08-30 15:12 ` Daniel Glöckner
2008-08-31 16:37 ` Andy Walls
[not found] ` <200809011144.54233.jdelvare@suse.de>
2008-09-01 12:35 ` Daniel Glöckner
[not found] ` <200809012126.06532.jdelvare@suse.de>
2008-09-01 22:54 ` Daniel Glöckner
[not found] ` <200809021109.31007.jdelvare@suse.de>
[not found] ` <200809021305.12318.jdelvare@suse.de>
2008-09-03 22:29 ` Daniel Glöckner
[not found] ` <200809051436.18549.jdelvare@suse.de>
2008-09-05 15:51 ` Daniel Glöckner
2008-09-05 19:16 ` [v4l-dvb-maintainer] " Trent Piepho
[not found] ` <200808281658.28151.jdelvare@suse.de>
2008-08-29 12:09 ` Andy Walls
2008-08-29 22:23 ` Trent Piepho
2008-08-30 0:10 ` Daniel Glöckner
[not found] ` <200808300954.19361.jdelvare@suse.de>
2008-08-30 16:44 ` Daniel Glöckner [this message]
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=20080830164444.GA263@daniel.bse \
--to=daniel-gl@gmx.net \
--cc=jdelvare@suse.de \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=video4linux-list@redhat.com \
--cc=xyzzy@speakeasy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox