On Sun, Sep 23, 2001 at 11:41:16PM +, ralf willenbacher wrote:
> that was me i guess.
> the rendering errors/lookups are likely the cause why it was never
> commited to a branch.
> the latest patch i found in my dri tree (16. jul) is attached.
> its a gl_decal fix and the agptex stuff.
> not m
On Sun, 23 Sep 2001 21:48, you wrote:
> Keith Whitwell wrote:
> > > Can I remove irq from the current branch? I have no option in BIOS
> > > that will
> > > disable IRQ for video, but If I had I suppose that DRM would manage
> > > with that. Can I simulate "no irq available"?
> >
> > Turning off
Keith Whitwell wrote:
>
> > Can I remove irq from the current branch? I have no option in BIOS that
> > will
> > disable IRQ for video, but If I had I suppose that DRM would manage with
> > that. Can I simulate "no irq available"?
>
> Turning off the irq in hardware won't help you, you need to
Keith Whitwell wrote:
> TAU wrote:
> >
> > Can you direct me on what should I do to get a cvs version working:
> > Where cvs is
> > what X11 parts should I compile and where to install
> > should I compile anything except i810 kmod for the kernel?
> > I can't find any ready RPMs for Mesa 3.5, sho
Keith Whitwell wrote:
> Michael Zayats wrote:
> >
> > The configuration is following:
> >
> > i810 + 2.4.3 + agpgart + 4.1.0 + kmod from 4.1.0
> >
> > I have the following problem:
> >
> > when drm loads (from /var/log/XFree86.0.log) it reports that
> > it can't register IRQ handler due to anothe
Bill Currie wrote:
>
> I've got the apg texturing patches applied to my checked out dri tree (trunk)
> and I was wondering if they've ever been committed to any branch of the dri
> cvs tree? I get the odd problem (programs using dri segfaulting at
> indeterminate occasions, corrupted textures, "o
OK, I have it working.
The problem was in dma_drm.h where 0 was passed
instead of SA_SHIRQ to request_irq call. That prevented it from sharing the
irq.
anything seems to work ok and I get 350 frames per
second in gears!
thanks for help Keith!
with best regards,
Michael
> Turning off the irq in hardware won't help you, you need to have a kernel
> module that doesn't rely on the irq. The i810 kernel module *will* share
irqs
> with other devices, but it sounds like your network card won't.
The message I get is:
(II) I810(0): [drm] failure adding irq handler, ther
Michael Zayats wrote:
>
> > > > 1) theoretic: Why at all drm needs IRQ i.e. does AGP sends info back
> to
> > > > the driver?
> > >
> > > The irq is removed in the mesa-3-5 branch. If you feel ok about
> > downloading,
> > > compiling and installing a cvs branch, you might be able rid of the
> >
TAU wrote:
>
> Can you direct me on what should I do to get a cvs version working:
> Where cvs is
> what X11 parts should I compile and where to install
> should I compile anything except i810 kmod for the kernel?
> I can't find any ready RPMs for Mesa 3.5, should I take it directly from
> Mesa s
El Dom 23 Sep 2001 04:50, escribiste:
> According to the register ref. (p.4-26), "GB" means "BGA package, AGP:
> both 1x and 2x)." I have an LT Pro, which has "LB" in the device ID.
> This is in the CFG_CHIP_TYPE in CONFIG_CHIP_ID. There's also a class,
> foundry ID, and major/minor numbers in C
> > > 1) theoretic: Why at all drm needs IRQ i.e. does AGP sends info back
to
> > > the driver?
> >
> > The irq is removed in the mesa-3-5 branch. If you feel ok about
> downloading,
> > compiling and installing a cvs branch, you might be able rid of the
> problem
> > that way. However, I don't
> > 1) theoretic: Why at all drm needs IRQ i.e. does AGP sends info back to
> > the driver?
>
> The irq is removed in the mesa-3-5 branch. If you feel ok about
downloading,
> compiling and installing a cvs branch, you might be able rid of the
problem
> that way. However, I don't know if Jeff has
13 matches
Mail list logo
