linux-kernel - Re: [PATCH] Patch pvr2 driver to allow development of maple bus driver

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]

Message-ID: <8b67d60708311314p39c7be30v630e97189d656abf@mail.gmail.com>
Date:	Fri, 31 Aug 2007 21:14:36 +0100
From:	"Adrian McMenamin" <lkmladrian@...il.com>
To:	"Mike Frysinger" <vapier.adi@...il.com>
Cc:	linux-kernel@...r.kernel.org, linuxsh-dev@...ts.sourceforge.net,
	"Paul Mundt" <lethal@...ux-sh.org>
Subject: Re: [PATCH] Patch pvr2 driver to allow development of maple bus driver

On 31/08/2007, Mike Frysinger <vapier.adi@...il.com> wrote:
> On 8/31/07, Adrian McMenamin <lkmladrian@...il.com> wrote:
> > This patch makes the PVR2 VBLANK interrupt on the SEGA Dreamcast
> > shareable - a small but necessary change to enable ongoing efforts to
> > develop a driver for the maple bus on the Dreamcast. (Maple is Sega's
> > proprietary serial interface for the Dreamcast and can be set to
> > synchronise dma transfers to the VBLANK).
> >
> > This has no impact on the performance of the PVR2.
>
> sharable implies the interrupt handler checks to see if it actually
> caused the interrupt ... which it doesnt at the moment ... presumably,
> you're making it shared because another device will be using that
> interrupt as well ... so when that other device gets an interrupt, how
> do you know it's for that device and not PVR2 ?


If the interrupt occurs then it will be for both of them. The hardware
cannot be removed and the maple bus driver is set for hardware sync.

The question seems redundant to me.
-
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/