public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "David Cooper" <david@forcedpotato.com>
Cc: "Ilguiz Latypov" <ilatypov@superbt.com>,
	"Linux MTD" <linux-mtd@lists.infradead.org>
Subject: Re: X Windows Performance with DOC 2000
Date: Fri, 21 Jun 2002 01:39:20 +0100	[thread overview]
Message-ID: <10120.1024619960@redhat.com> (raw)
In-Reply-To: <AIEOIMKIOAAJKHJOGAEFGEFACEAA.david@forcedpotato.com>

david@forcedpotato.com said:
>  Yes, when I use a kernel with the MTD support built-in for DoC 2000
> and nftl I can still run X with the DoC in the system (unless I use
> the M-Systems 4.2 firmware which prevents X from running with or
> without MTD support).  I have not tried loading and unloading MTD
> support as a kernel module.  Maybe this is worth a go. 

If you have the drivers built-in and can still run X, that's what I wanted 
to know. Can you even have the file system on NFTL mounted, as long as your 
X modules aren't on it?

>  Interestingly, I can run SVGAlib applications from the DoC (using the
> VESA driver) without any trouble.  This is confusing because I would
> imagine that the SVGAlib VESA driver and the XFree86 VESA driver are
> both accessing the VESA BIOS.

True.

> M-Systems have told me that the firmware DoC driver that loads into
> memory at bootup sometimes conflicts in memory space that linux is
> trying to use. I suppose this would explain why using different
> firmware versions can prevent X from running from the IDE drive. 

That caused Linux to fail to boot -- but once you're actually in Linux, 
the allocations of the old DOS driver should be long forgotten.

Unless the XFree86 code somehow tries to re-run the DiskOnChip firmware -- 
but you said you'd reproduced the problem even with that obliterated, 
didn't you?

--
dwmw2

  reply	other threads:[~2002-06-21  0:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-14  3:09 X Windows Performance with DOC 2000 David Cooper
2002-06-15 22:32 ` Charles Manning
2002-06-17 22:30   ` David Cooper
2002-06-17 22:32     ` Ilguiz Latypov
2002-06-18  0:22       ` David Cooper
2002-06-18  0:40         ` Brendan J Simon
2002-06-21 23:33           ` Christopher Fowler
2002-06-18 14:11         ` Ilguiz Latypov
2002-06-20 19:41           ` David Cooper
2002-06-20 21:59             ` David Woodhouse
2002-06-21  0:33               ` David Cooper
2002-06-21  0:39                 ` David Woodhouse [this message]
2002-06-21  5:46                   ` David Cooper
2002-06-21  7:04                     ` David Woodhouse
2002-06-26 18:30                       ` David Cooper
2002-06-26 21:28                         ` David Woodhouse
2002-06-21 13:56                     ` Ilguiz Latypov
2002-06-21 14:09                       ` cfowler
2002-06-21 14:12                         ` David Woodhouse
2002-06-21 14:28                           ` cfowler
2002-06-22  0:01                             ` Ilguiz Latypov
2002-06-22  0:15                               ` Christopher Fowler
2002-06-22  1:14                                 ` David Cooper
2002-06-22  1:11                                   ` Gonzalo Servat
2002-06-22  9:18                                 ` David Woodhouse

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=10120.1024619960@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=david@forcedpotato.com \
    --cc=ilatypov@superbt.com \
    --cc=linux-mtd@lists.infradead.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