mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chris Rutherford" <chris1@hackinghardware.com>
To: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: pci bridge 0000:00:1c.1 compaq nc8230 laptop
Date: Tue, 20 Sep 2005 17:49:41 +0100	[thread overview]
Message-ID: <002b01c5be03$4bf25840$6401a8c0@CMR> (raw)

Hi All,

This is my first email to the lkml so kindly forgive me if I appear 
naive.

I have a compaq nc8230 laptop with a TPM which I am 'playing with'.

I have successfully compiled and patched previous kernel versions 
2.6.6 to 2.6.12 and as of patching 2.6.12 with the TPM libraries I was 
able to access the tpm using an Intel motherboard but not the Compaq 
machine.

Unfortunately the tpm libries in the 2.6.12 kernel were not combatable 
with the Compaq tpm implementation and I was not able to locate the 
TPM address or device and the kernel module could not find the TPM IC.

As of 2.6.13 the TPM code has been properly integrated with the kernel 
and I was hoping to get the TPM working on my laptop.  Although I 
could successfully get the 2.6.12, to compile and run on the nc8230, 
as of 2.6.13 I have been getting the following crash when I start the 
kernel :-

PCI: Cannot allocate resource region 7 of bridge 0000:00:1c.1
PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.1
PCI: Cannot allocate resource region 9 of bridge 0000:00:1c.1

 I have seen the 00:1c.1 device problem in the lkml archive, however 
im not sure exactly what the problem is.  I thought I'd let you all 
know that something has happened to the new kernel that stops it 
working on the compaq nc8230 laptop.  I would very much like to know 
if this problem is known and if it is going to be fixed in the 2.6.14 
release.

Thanks

Chris R





             reply	other threads:[~2005-09-20 16:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-20 16:49 Chris Rutherford [this message]
2005-10-19 22:25 Chris Rutherford

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='002b01c5be03$4bf25840$6401a8c0@CMR' \
    --to=chris1@hackinghardware.com \
    --cc=linux-kernel@vger.kernel.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

Powered by JetHome