On Wed, 2005-03-09 at 12:45 +0200, Pekka Enberg wrote:
> Hi Benjamin,
>
> Few coding style nitpicks follow.
>
> On Tue, 08 Mar 2005 18:11:59 +1100, Benjamin Herrenschmidt
> <[EMAIL PROTECTED]> wrote:
> > Index: linux-work/include/linux/pci.h
> >
Il Wed, Mar 09, 2005 at 09:46:20AM +1100, Benjamin Herrenschmidt ha scritto:
> One thing is: I
> don't have x86 hardware, or at least, nothing where I can have 2 VGA
> cards in (I may have access to an old laptop). So I'll need help &
> testers at one point.
It's your lucky day ;) I've just
On Tuesday, March 8, 2005 9:58 pm, Jon Smirl wrote:
> On Wed, 09 Mar 2005 16:37:13 +1100, Benjamin Herrenschmidt
>
> <[EMAIL PROTECTED]> wrote:
> > On Tue, 2005-03-08 at 23:35 -0500, Jon Smirl wrote:
> > > This is from /linux-2.5/Documentation/filesystems/sysfs-pci.txt. It
> > > describes how ia64
Hi Benjamin,
Few coding style nitpicks follow.
On Tue, 08 Mar 2005 18:11:59 +1100, Benjamin Herrenschmidt
<[EMAIL PROTECTED]> wrote:
> Index: linux-work/include/linux/pci.h
> ===
> --- linux-work.orig/include/linux/pci.h
Hi Benjamin,
On Tue, 2005-03-08 at 22:29 +0100, Kronos wrote:
> > kfree(NULL) is fine, no need to check for null pointer.
On Wed, 09 Mar 2005 09:46:20 +1100, Benjamin Herrenschmidt
<[EMAIL PROTECTED]> wrote:
> Hehe, yes, but I don't like it :)
Please consider doing that anyway as there are
Ok, here's today status. I posted the patch at
http://gate.crashing.org/~benh/vga-arbiter.diff. I fixed some issues &
added support for nesting locks, I added comments/documentation to
kernel interface. It's not tested yet. It's not complete neither, the
userland interface is partially implemented
Ok, here's today status. I posted the patch at
http://gate.crashing.org/~benh/vga-arbiter.diff. I fixed some issues
added support for nesting locks, I added comments/documentation to
kernel interface. It's not tested yet. It's not complete neither, the
userland interface is partially implemented
Hi Benjamin,
On Tue, 2005-03-08 at 22:29 +0100, Kronos wrote:
kfree(NULL) is fine, no need to check for null pointer.
On Wed, 09 Mar 2005 09:46:20 +1100, Benjamin Herrenschmidt
[EMAIL PROTECTED] wrote:
Hehe, yes, but I don't like it :)
Please consider doing that anyway as there are ongoing
Hi Benjamin,
Few coding style nitpicks follow.
On Tue, 08 Mar 2005 18:11:59 +1100, Benjamin Herrenschmidt
[EMAIL PROTECTED] wrote:
Index: linux-work/include/linux/pci.h
===
--- linux-work.orig/include/linux/pci.h 2005-01-24
On Tuesday, March 8, 2005 9:58 pm, Jon Smirl wrote:
On Wed, 09 Mar 2005 16:37:13 +1100, Benjamin Herrenschmidt
[EMAIL PROTECTED] wrote:
On Tue, 2005-03-08 at 23:35 -0500, Jon Smirl wrote:
This is from /linux-2.5/Documentation/filesystems/sysfs-pci.txt. It
describes how ia64 is achieving
Il Wed, Mar 09, 2005 at 09:46:20AM +1100, Benjamin Herrenschmidt ha scritto:
One thing is: I
don't have x86 hardware, or at least, nothing where I can have 2 VGA
cards in (I may have access to an old laptop). So I'll need help
testers at one point.
It's your lucky day ;) I've just assembled
On Wed, 2005-03-09 at 12:45 +0200, Pekka Enberg wrote:
Hi Benjamin,
Few coding style nitpicks follow.
On Tue, 08 Mar 2005 18:11:59 +1100, Benjamin Herrenschmidt
[EMAIL PROTECTED] wrote:
Index: linux-work/include/linux/pci.h
On Wed, 2005-03-09 at 00:58 -0500, Jon Smirl wrote:
> On Wed, 09 Mar 2005 16:37:13 +1100, Benjamin Herrenschmidt
> <[EMAIL PROTECTED]> wrote:
> > On Tue, 2005-03-08 at 23:35 -0500, Jon Smirl wrote:
> > > This is from /linux-2.5/Documentation/filesystems/sysfs-pci.txt. It
> > > describes how ia64
On Wed, 09 Mar 2005 16:37:13 +1100, Benjamin Herrenschmidt
<[EMAIL PROTECTED]> wrote:
> On Tue, 2005-03-08 at 23:35 -0500, Jon Smirl wrote:
> > This is from /linux-2.5/Documentation/filesystems/sysfs-pci.txt. It
> > describes how ia64 is achieving legacy IO. The VGA control code
> > probably
On Tue, 2005-03-08 at 23:35 -0500, Jon Smirl wrote:
> This is from /linux-2.5/Documentation/filesystems/sysfs-pci.txt. It
> describes how ia64 is achieving legacy IO. The VGA control code
> probably needs to be coordinated with this.
This is a different thing, and I will implement it on ppc one
This is from /linux-2.5/Documentation/filesystems/sysfs-pci.txt. It
describes how ia64 is achieving legacy IO. The VGA control code
probably needs to be coordinated with this.
--
Accessing legacy resources through sysfs
On Tue, 2005-03-08 at 22:17 -0500, Jon Smirl wrote:
> How do I do the 'disable all, post, renable last active' sequence in
> this scheme?
You don't do it that way. You vga_get(IO|MEM) the card you want to
POST, do the POST, then vga_put().
Subsequent user will get back ownership when it does
How do I do the 'disable all, post, renable last active' sequence in
this scheme?
--
Jon Smirl
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Tue, 2005-03-08 at 18:47 -0500, Jon Smirl wrote:
> This very similar to the reset support patch I have been working on.
>
> In the reset patch there is a 'vga' attribute on each VGA device. Set
> it to 0/1 to make the device active. This lets you move the console
> around betweem VGA devices.
This very similar to the reset support patch I have been working on.
In the reset patch there is a 'vga' attribute on each VGA device. Set
it to 0/1 to make the device active. This lets you move the console
around betweem VGA devices.
You can also set it to 3, which disables all VGA devices but
On Tue, 2005-03-08 at 22:29 +0100, Kronos wrote:
> > + bus = pdev->bus;
> > + while (bus) {
> > + bridge = bus->self;
> > + if (bridge) {
> > + pci_read_config_word(bridge, PCI_BRIDGE_CONTROL,
> > );
> > + if
Minus the big fat ugly bug of scheduling with a spinlock in vga_get() of
course ... bah. Easy to fix tho. I'll post a new version later.
Ben.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Benjamin Herrenschmidt <[EMAIL PROTECTED]> ha scritto:
> Ok, so here is a first, totally untested draft for the kernel side
> of the VGA arbiter.
Hi Ben,
I've a few comments:
> Index: linux-work/drivers/pci/vga.c
> ===
> ---
Benjamin Herrenschmidt [EMAIL PROTECTED] ha scritto:
Ok, so here is a first, totally untested draft for the kernel side
of the VGA arbiter.
Hi Ben,
I've a few comments:
Index: linux-work/drivers/pci/vga.c
===
--- /dev/null
Minus the big fat ugly bug of scheduling with a spinlock in vga_get() of
course ... bah. Easy to fix tho. I'll post a new version later.
Ben.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Tue, 2005-03-08 at 22:29 +0100, Kronos wrote:
+ bus = pdev-bus;
+ while (bus) {
+ bridge = bus-self;
+ if (bridge) {
+ pci_read_config_word(bridge, PCI_BRIDGE_CONTROL,
cmd);
+ if (!(cmd
This very similar to the reset support patch I have been working on.
In the reset patch there is a 'vga' attribute on each VGA device. Set
it to 0/1 to make the device active. This lets you move the console
around betweem VGA devices.
You can also set it to 3, which disables all VGA devices but
On Tue, 2005-03-08 at 18:47 -0500, Jon Smirl wrote:
This very similar to the reset support patch I have been working on.
In the reset patch there is a 'vga' attribute on each VGA device. Set
it to 0/1 to make the device active. This lets you move the console
around betweem VGA devices.
How do I do the 'disable all, post, renable last active' sequence in
this scheme?
--
Jon Smirl
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Tue, 2005-03-08 at 22:17 -0500, Jon Smirl wrote:
How do I do the 'disable all, post, renable last active' sequence in
this scheme?
You don't do it that way. You vga_get(IO|MEM) the card you want to
POST, do the POST, then vga_put().
Subsequent user will get back ownership when it does
This is from /linux-2.5/Documentation/filesystems/sysfs-pci.txt. It
describes how ia64 is achieving legacy IO. The VGA control code
probably needs to be coordinated with this.
--
Accessing legacy resources through sysfs
On Tue, 2005-03-08 at 23:35 -0500, Jon Smirl wrote:
This is from /linux-2.5/Documentation/filesystems/sysfs-pci.txt. It
describes how ia64 is achieving legacy IO. The VGA control code
probably needs to be coordinated with this.
This is a different thing, and I will implement it on ppc one of
On Wed, 09 Mar 2005 16:37:13 +1100, Benjamin Herrenschmidt
[EMAIL PROTECTED] wrote:
On Tue, 2005-03-08 at 23:35 -0500, Jon Smirl wrote:
This is from /linux-2.5/Documentation/filesystems/sysfs-pci.txt. It
describes how ia64 is achieving legacy IO. The VGA control code
probably needs to be
On Wed, 2005-03-09 at 00:58 -0500, Jon Smirl wrote:
On Wed, 09 Mar 2005 16:37:13 +1100, Benjamin Herrenschmidt
[EMAIL PROTECTED] wrote:
On Tue, 2005-03-08 at 23:35 -0500, Jon Smirl wrote:
This is from /linux-2.5/Documentation/filesystems/sysfs-pci.txt. It
describes how ia64 is achieving
Hi !
Ok, so here is a first, totally untested draft for the kernel side
of the VGA arbiter.
BIG NOTE: It's really only the basic arbiter itself, which provides the
API I drafted a bit earlier, with arch hooks similar to what Alan proposed,
it does _NOT_ yet provides a userland interface (to a
Hi !
Ok, so here is a first, totally untested draft for the kernel side
of the VGA arbiter.
BIG NOTE: It's really only the basic arbiter itself, which provides the
API I drafted a bit earlier, with arch hooks similar to what Alan proposed,
it does _NOT_ yet provides a userland interface (to a
36 matches
Mail list logo
