All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-kernel@vger.kernel.org
Subject: opinions on bigphysarea and DSDT-in-initrd patches
Date: Wed, 8 Mar 2006 21:48:13 -0600	[thread overview]
Message-ID: <20060309034813.GA5300@dbz.icequake.net> (raw)

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


Hi,

I grepped through the latest ML digests and didn't see any mention of
these patches recently.  I was wondering what the general opinion was on
potentially merging them.  They are both hardware support patches.  I
asked about the Debian kernel team maintaining them of instead
linux-kernel, but met with a lack of response there.

First is bigphysarea:
http://pv105234.reshsg.uci.edu/~jfeise/Downloads/zr36120/
This is necessary for hardware which doesn't support scatter gather DMA.
It is non invasive since it only becomes activated when the user
supplies a kernel cmdline argument.  I've tested the latest version and
it works fine.

Also, I'm wondering if it is possible to include ACPI DSDT-in-initrd
patch on ACPI-supported platforms (i386, x86-64 and ia64 AFAIK).
http://gaugusch.at/kernel.shtml

This saves a user from having to rebuild the entire kernel when his
firmware DSDT either has known bugs, or he is in the process of
debugging it.  In fact it would have saved me a whole lot of time this
week.

Note that this is different from the DSDT-append-to-initrd approach that
was discussed previously.  I think it is a better design now, but
curious about your thoughts.

Thanks,

-- 
Ryan Underwood, <nemesis@icequake.net>

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2006-03-09  3:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20060309034813.GA5300@dbz.icequake.net \
    --to=nemesis-lists@icequake.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nemesis@icequake.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.