Kylene Jo Hall wrote: >>You wouldn't happen to have just your patches available? >> >> > >Here is the tpm portion of -mm patch > > > Thanks. I've tried the patch and everthing seems to work fine now. :) (btw. does no output in dmesg mean that no TPM chip was found? it seems to have found a pci id it likes atleast.) Rgds Pierre - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: 2.6.12 breaks 8139cp
- From: Kylene Jo Hall <[email protected]>
- Re: 2.6.12 breaks 8139cp
- References:
- 2.6.12 breaks 8139cp
- From: Pierre Ossman <[email protected]>
- Re: 2.6.12 breaks 8139cp
- From: Bjorn Helgaas <[email protected]>
- Re: 2.6.12 breaks 8139cp
- From: Pierre Ossman <[email protected]>
- Re: 2.6.12 breaks 8139cp
- From: Bjorn Helgaas <[email protected]>
- Re: 2.6.12 breaks 8139cp
- From: Pierre Ossman <[email protected]>
- Re: 2.6.12 breaks 8139cp
- From: Pierre Ossman <[email protected]>
- Re: 2.6.12 breaks 8139cp
- From: Pierre Ossman <[email protected]>
- Re: 2.6.12 breaks 8139cp
- From: Kylene Jo Hall <[email protected]>
- Re: 2.6.12 breaks 8139cp
- From: Pierre Ossman <[email protected]>
- Re: 2.6.12 breaks 8139cp
- From: Kylene Jo Hall <[email protected]>
- 2.6.12 breaks 8139cp
- Prev by Date: Re: tungsten t5 doesn't sync anymore with kernel 2.6.12
- Next by Date: Re: [PATCH 2/6] Rename __lock_page to lock_page_slow
- Previous by thread: Re: 2.6.12 breaks 8139cp
- Next by thread: Re: 2.6.12 breaks 8139cp
- Index(es):
 |