linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Jahns <Thomas.Jahns@epost.de>
To: David Eger <eger@havoc.gtf.org>
Cc: Thomas Jahns <Thomas.Jahns@epost.de>,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Mach64 GX driver problems in post 2.4.22 kernels
Date: Thu, 24 Jun 2004 22:37:58 +0200	[thread overview]
Message-ID: <20040624203758.GE1965@mercury.jahnsnet.de> (raw)
In-Reply-To: <20040621080858.GA11936@havoc.gtf.org> (from eger@havoc.gtf.org on Mon, Jun 21, 2004 at 10:08:58 +0200)

[-- Attachment #1: Type: text/plain, Size: 2687 bytes --]

On 06/21/04 10:08:58, David Eger wrote:
> 
> Could you send your .config?  (This could only help with the most
> trivial of problems, but worth a shot.)

Okay, I'll bzip the .configs and also include a diff I created from  
both files with the following sequence of commands (tungsten is the  
hostname of the Pmac in question):

 > grep -v '^#' ../boot/config-2.4.22-tungsten >config-2.4.22-tungsten. 
cleanup
 > grep -v '^#' ../boot/config-2.4.25-tungsten >config-2.4.25-tungsten. 
cleanup
 > diff -u config-2.4.2*cleanup >dot.config.diff-u

see below for the diff. PREEMPT is no longer selected because this diff  
is already for a kernel configuration that I did not patch as much as  
the working 2.4.22 kernel to limit the potential error sources.

> You're posting to the right list; you're probably not getting
> responses because none of the active framebuffer developers have a  
> setup similar enough to yours :-/

That's unfortunate, I think quite a number of Macs in the 9500 and 9600  
lines came preinstalled with such cards and ATI cards were also a  
popular upgrade for Mac graphics at that time.

> At least, that's why I'd not responded... still trying to debug  
> radeon and cirrus...

I'm also a user of the radeon driver so keep up the good work.

Ciao, Thomas

--- config-2.4.22-tungsten.cleanup	2004-06-24 22:30:01.000000000  
+0200
+++ config-2.4.25-tungsten.cleanup	2004-06-24 22:30:07.000000000  
+0200
@@ -11,9 +11,12 @@
 CONFIG_6xx=y
 CONFIG_PPC_STD_MMU=y
 CONFIG_ALL_PPC=y
-CONFIG_PREEMPT=y
 CONFIG_PPC_ISATIMER=y

+CONFIG_HIGHMEM_START=0xfe000000
+CONFIG_LOWMEM_SIZE=0x30000000
+CONFIG_KERNEL_START=0xc0000000
+CONFIG_TASK_SIZE=0x80000000
 CONFIG_PCI=y
 CONFIG_NET=y
 CONFIG_SYSCTL=y
@@ -93,6 +96,10 @@
 CONFIG_IP_NF_TARGET_LOG=m
 CONFIG_IP_NF_TARGET_ULOG=m
 CONFIG_IP_NF_TARGET_TCPMSS=m
+
+
+CONFIG_IPV6_SCTP__=y
+
 CONFIG_ATALK=m


@@ -100,6 +107,7 @@


 CONFIG_SCSI=y
+
 CONFIG_BLK_DEV_SD=y
 CONFIG_SD_EXTRA_DEVS=40
 CONFIG_CHR_DEV_ST=y
@@ -107,6 +115,7 @@
 CONFIG_BLK_DEV_SR_VENDOR=y
 CONFIG_SR_EXTRA_DEVS=2
 CONFIG_CHR_DEV_SG=m
+
 CONFIG_SCSI_CONSTANTS=y

 CONFIG_SCSI_AIC7XXX_OLD=y
@@ -178,9 +187,12 @@



+
 CONFIG_NVRAM=y

+
 CONFIG_DRM=y
+
 CONFIG_DRM_NEW=y
 CONFIG_DRM_R128=m

@@ -218,11 +230,9 @@

 CONFIG_NFS_FS=m
 CONFIG_NFS_V3=y
-CONFIG_NFS_ACL=y
 CONFIG_NFS_DIRECTIO=y
 CONFIG_NFSD=m
 CONFIG_NFSD_V3=y
-CONFIG_NFSD_ACL=y
 CONFIG_NFSD_TCP=y
 CONFIG_SUNRPC=m
 CONFIG_LOCKD=m
@@ -251,6 +261,9 @@
 CONFIG_SOUND=y
 CONFIG_DMASOUND_PMAC=m
 CONFIG_DMASOUND=m
+CONFIG_I2C=m
+CONFIG_I2C_KEYWEST=m
+



@@ -273,6 +286,6 @@
 CONFIG_CRC32=m
 CONFIG_ZLIB_INFLATE=m
 CONFIG_ZLIB_DEFLATE=m
-CONFIG_QSORT=y

 CONFIG_BOOTX_TEXT=y
+CONFIG_LOG_BUF_SHIFT=0


[-- Attachment #2: config-2.4.22-tungsten.bz2 --]
[-- Type: application/x-bzip, Size: 4186 bytes --]

[-- Attachment #3: config-2.4.25-tungsten.bz2 --]
[-- Type: application/x-bzip, Size: 4035 bytes --]

  parent reply	other threads:[~2004-06-24 21:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-05 18:56 Mach64 GX driver problems in post 2.4.22 kernels Thomas Jahns
2004-06-06 10:45 ` Thomas Jahns
2004-06-18  9:48   ` Thomas Jahns
2004-06-21  8:08     ` David Eger
2004-06-21  8:52       ` Geert Uytterhoeven
2004-06-24 20:37       ` Thomas Jahns [this message]
2004-06-23 18:31     ` David Eger
2004-06-24 21:20       ` Thomas Jahns

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=20040624203758.GE1965@mercury.jahnsnet.de \
    --to=thomas.jahns@epost.de \
    --cc=eger@havoc.gtf.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).