Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Arnt Karlsen <arnt@c2i.net>
To: netfilter@lists.netfilter.org
Subject: OT: video cards, was: more questions about kernel config options for iptables
Date: Tue, 8 Apr 2003 20:27:00 +0200	[thread overview]
Message-ID: <20030408202700.1686bfde.arnt@c2i.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0304081107590.11474-100000@dell>

On Tue, 8 Apr 2003 11:11:23 -0400 (EDT), 
"Robert P. J. Day" <rpjday@mindspring.com> wrote in message 
<Pine.LNX.4.44.0304081107590.11474-100000@dell>:

> On Tue, 8 Apr 2003, Joel Newkirk wrote:
> 
> > OT - are there any plans to bring video card options together,
> > instead of the current scheme where they are scattered through
> > Character Devices, Multimedia Devices, and Console Drivers?
> 
> <sigh>.  i was looking at that and, as i mentioned, took a crack
> at reorg'ing the filesystems menu in the most recent 2.5.6x
> kernels.
> 
> sadly, that was pretty easy since the Kconfig files and associated
> source files were in the same directory.  so cleaning up a *single*
> menu or submenu is not hard.
> 
> but it's clear that there is stuff scattered all over the menu
> structure that should be related.  the difficulty there is that
> different people are responsible for different subsystems,
> and look after their own directory structure.  so that makes it
> *way* more difficult to bring together options in distant
> menus.
> 
> i'm trying to do this a little at a time; hence the attempt
> to deal with the netfilter stuff as a start.  one level higher
> up, it's clear that the entire networking options menu could
> stand some cleaning.
> 

..ok, I the video newbie volonteer as guineapig with: 
Bus  1, device   0, function  0:
    VGA compatible controller: ATI Technologies Inc 3D Rage IIC AGP 
(rev 122).      
      IRQ 11.
      Master Capable.  Latency=64.  Min Gnt=8.
      Prefetchable 32 bit memory at 0xea000000 [0xeaffffff].
      I/O at 0xd000 [0xd0ff].
      Non-prefetchable 32 bit memory at 0xe9000000 [0xe9000fff].

...and:
Bus  0, device  15, function  0:
    VGA compatible controller: ATI Technologies Inc 3D Rage II+ 
215GTB  [Mach64 GTB] (rev 154).      
      Master Capable.  Latency=32.  Min Gnt=8.
      Non-prefetchable 32 bit memory at 0xe0000000 [0xe0ffffff].
      I/O at 0x6600 [0x66ff].
      Non-prefetchable 32 bit memory at 0xe1000000 [0xe1000fff].


-- 
..med vennlig hilsen = with Kind Regards from Arnt... ;-)
...with a number of polar bear hunters in his ancestry...
  Scenarios always come in sets of three: 
  best case, worst case, and just in case.



  reply	other threads:[~2003-04-08 18:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07 21:18 more questions about kernel config options for iptables Robert P. J. Day
2003-04-08  7:04 ` Joel Newkirk
2003-04-08  7:44   ` Joel Newkirk
2003-04-08 11:17     ` Arnt Karlsen
2003-04-08 11:01   ` Robert P. J. Day
2003-04-08 11:55     ` Cedric Blancher
2003-04-08 12:23       ` Robert P. J. Day
2003-04-08 12:59         ` Cedric Blancher
2003-04-08 13:04           ` Robert P. J. Day
2003-04-08 13:54           ` Robert P. J. Day
2003-04-08 15:09             ` Joel Newkirk
2003-04-08 15:11               ` Robert P. J. Day
2003-04-08 18:27                 ` Arnt Karlsen [this message]
2003-04-09  1:25               ` indev/outdev_name? Scott MacKay

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=20030408202700.1686bfde.arnt@c2i.net \
    --to=arnt@c2i.net \
    --cc=netfilter@lists.netfilter.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