lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 3 Nov 2006 01:28:38 +0300
From:	Ivan Kokshaysky <ink@...assic.park.msu.ru>
To:	Andrew Morton <akpm@...l.org>
Cc:	Steve Langasek <vorlon@...ian.org>, Eki <eki@....fi>,
	Richard Henderson <rth@...ddle.net>,
	linux-kernel@...r.kernel.org, thias.lelourd@...il.com,
	jharrison@...uxbs.org
Subject: Re: [patch] video: support for VGA hoses on alpha TITAN, TSUNAMI systems (ES45, DS25)

On Thu, Nov 02, 2006 at 01:14:43PM -0800, Andrew Morton wrote:
> What is a "hose"?

A real name of "pci domain". ;-)

> > +	/* First, fixup the VGA resource bounds WRT the hose it is on. */
> > +	if (pci_vga_hose) {
> > +		new->start += pci_vga_hose->io_space->start;
> > +		new->end += pci_vga_hose->io_space->start;
> > +	}
> > +
> > +	/* Finally, do a normal request_resource(). */
> > +	return request_resource(root, new);

This will always fail. Should be

	return request_resource(pci_vga_hose->io_space, new);

> > +}
> > 
> 
> So if the resource is being requested by vga we adjust the caller's
> resource before actually requesting it.
> 
> Isn't this a bit hacky?  How come vgacon ended up requesting the wrong
> addresses in the first place?

vgacon requests the correct _bus_ address, but it doesn't work with
multiple buses. So a fixup similar to pcibios_fixup_resource() or
pcibios_bus_to_resource() is needed.

Ivan.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ