Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Vorobiev Dmitri <dmitri.vorobiev@movial.fi>, linux-mips@linux-mips.org
Subject: Re: [PATCH] [MIPS] Remove unused header file gio.h
Date: Thu, 27 Nov 2008 12:34:53 +0100	[thread overview]
Message-ID: <20081127113453.GA7618@alpha.franken.de> (raw)
In-Reply-To: <20081127112234.GA20189@linux-mips.org>

On Thu, Nov 27, 2008 at 11:22:34AM +0000, Ralf Baechle wrote:
> On Thu, Nov 27, 2008 at 11:37:06AM +0100, Thomas Bogendoerfer wrote:
> 
> > first step is to introduce GIO devices similair to PCI devices. My
> > current working GIO device is solid impact. I also looked at
> > supporting Phobos G160 cards, but the current set of 2114x drivers
> > is not useable for that...
> > 
> > The big missing thing in the GIO framework right now is a bullet proof
> > detection for non standard GIO cards, like newport and XZ cards. They
> > don't provide ID information...
> 
> So the resulting code will be a mix of normal probing bus code and
> something like "GIO platform devices" which are just added if we somehow
> "know" they're there?  SGI never stops to amaze me ...

Newport and XZ are probeable somehow, PROM and IRIX gfxinit are able
to do that. I want to integrate the documented probing and the special
probes into the GIO framework.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2008-11-27 11:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-26 13:34 [PATCH] [MIPS] Remove unused header file gio.h Dmitri Vorobiev
2008-11-27  9:16 ` Thomas Bogendoerfer
2008-11-27 10:24   ` Vorobiev Dmitri
2008-11-27 10:37     ` Thomas Bogendoerfer
2008-11-27 11:22       ` Ralf Baechle
2008-11-27 11:34         ` Thomas Bogendoerfer [this message]
2008-11-27 18:39       ` Kumba

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=20081127113453.GA7618@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=dmitri.vorobiev@movial.fi \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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