Date: Mon, 07 Oct 2013 12:17:31 -0500 From: Jim Bryant <kc5vdj.freebsd@gmail.com> To: tzoi516 <tzoi516@gmail.com> Cc: freebsd-drivers@freebsd.org Subject: Re: Latitude E6400 Drivers Message-ID: <5252ECAB.8060706@gmail.com> In-Reply-To: <5252EA1F.5030802@gmail.com> References: <5251A405.1010304@gmail.com> <CAEJt7hbefd4pVeLGqA24uy=Fghairk47MPWbT5SfPgnjWTNvWQ@mail.gmail.com> <5252EA1F.5030802@gmail.com>
index | next in thread | previous in thread | raw e-mail
IIRC, the AMT is the remote management interface. You really don't need it, unless you intend to do something with it. http://software.intel.com/en-us/articles/intel-active-management-technology-start-here-guide-intel-amt-9 tzoi516 wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I was able to get all of the drivers working except for this one: > > none0@pci0:0:3:3: class=0x070002 card=0x02331028 chip=0x2a478086 > rev=0x07 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Mobile 4 Series Chipset AMT SOL Redirection' > class = simple comms > subclass = UART > bar [10] = type I/O Port, range 32, base 0xef88, size 8, enabled > bar [14] = type Memory, range 32, base 0xf6fda000, size 4096, > enabled > cap 01[c8] = powerspec 3 supports D0 D3 current D0 > cap 05[d0] = MSI supports 1 message, 64 bit > > The following items are what I used in loader.conf: > > mmc_load="YES" > mmcsd_load="YES" > sdhci_load="YES" # Richoh R5C822 > ichsmb_load="YES" # 82801I (ICH9 Family) SMBus Controller > firewire_load="YES" > > Finally got the HECI code to compile, which took care of the MEI > driver. I'm trying to figure out out to compile the Linux OpenAMT to > clear the last one. Thank you very much Henry for the help. > > > On 10/06/13 15:07, Henry Hu wrote: > >> >> On Sun, Oct 6, 2013 at 1:55 PM, tzoi516 <tzoi516@gmail.com >> <mailto:tzoi516@gmail.com>> wrote: >> >> Hi, >> >> I'm able to find solutions to most drivers, but I'm having trouble >> determining what to load for these: >> >> none0@pci0:0:3:0: class=0x078000 card=0x02331028 >> chip=0x2a448086 rev=0x07 hdr=0x00 vendor = 'Intel Corporation' >> device = 'Mobile 4 Series Chipset MEI Controller' class = >> simple comms bar [10] = type Memory, range 64, base 0xf6fd9ef0, >> size 16, enabled cap 01[50] = powerspec 3 supports D0 D3 current >> D0 cap 05[8c] = MSI supports 1 message, 64 bit >> >> >> >>> I also have this on my laptop and I think this may be an >>> experimental driver: >>> http://lists.freebsd.org/pipermail/freebsd-acpi/2009-October/006078.html >>> >>> >>> > But I've not tried it. > >> >> none1@pci0:0:3:3: class=0x070002 card=0x02331028 >> chip=0x2a478086 rev=0x07 hdr=0x00 vendor = 'Intel Corporation' >> device = 'Mobile 4 Series Chipset AMT SOL Redirection' class >> = simple comms subclass = UART bar [10] = type I/O Port, range >> 32, base 0xef88, size 8, enabled bar [14] = type Memory, range >> 32, base 0xf6fda000, size 4096, enabled cap 01[c8] = powerspec 3 >> supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 >> bit >> >> none2@pci0:0:31:3: class=0x0c0500 card=0x02331028 >> chip=0x29308086 rev=0x03 hdr=0x00 vendor = 'Intel Corporation' >> device = '82801I (ICH9 Family) SMBus Controller' class = >> serial bus subclass = SMBus bar [10] = type Memory, range 64, >> base 0xf6fd9f00, size 256, enabled bar [20] = type I/O Port, >> range 32, base 0x1100, size 32, enabled >> >> >> >>> You can look at /sys/modules/i2c and modules under it. >>> >> >> none3@pci0:3:1:1: class=0x080501 card=0x02331028 >> chip=0x08221180 rev=0x21 hdr=0x00 vendor = 'Ricoh Co Ltd' >> device = 'R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter' class >> = base peripheral subclass = SD host controller bar [10] = type >> Memory, range 32, base 0xf1bff600, size 256, enabled cap 01[80] = >> powerspec 2 supports D0 D1 D2 D3 current D0 >> >> none4@pci0:3:1:2: class=0x088000 card=0x02331028 >> chip=0x08431180 rev=0x11 hdr=0x00 vendor = 'Ricoh Co Ltd' >> device = 'R5C843 MMC Host Controller' class = base >> peripheral bar [10] = type Memory, range 32, base 0xf1bff700, >> size 256, enabled cap 01[80] = powerspec 2 supports D0 D1 D2 D3 >> current D0 >> >> >> >>> As I remember my old laptop with Ricoh MMC controller works with >>> sdhci & mmc & mmcsd. According to sdhci(4), it works with RICOH >>> R5C822. Your chip's id seems to match with that one, so you can >>> try to modify that driver a bit to make it recognize your >>> device? >>> >> I know people are busy, but any links or references to help find >> drivers or modules would be appreciated. I've used man and PCI >> driver sites to help narrow down, but nothing helped. mmc and mmcsd >> modules don't work with the Ricoh devices, per pciconf. Thanks. >> >> _______________________________________________ >> freebsd-drivers@freebsd.org <mailto:freebsd-drivers@freebsd.org> >> mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-drivers To >> unsubscribe, send any mail to >> "freebsd-drivers-unsubscribe@freebsd.org >> <mailto:freebsd-drivers-unsubscribe@freebsd.org>" >> >> >> >> >> -- Cheers, Henry >> > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.19 (FreeBSD) > Comment: Using GnuPG with undefined - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJSUuofAAoJEDHcsSNRIRfJ0j4H/icDXP5u63rFkvPWC7wHwwZv > 46XE9Bn6Y1EJURjnyIzEgmyVsnGw0MNL8vLbGUSdTSW6KTen0j4fyP85+wU6QG4m > M8Axd5OUAKjgX+SiTapMGEtpy9UdHEegxPrIPtomcxeYVk7/5Zj7dm8xLDc4TsWl > 5lfAu4gLkwsw7EJpp6N+jnzVxtTzOfUF9GgmT4EudAFWr9rNRhZyxhjZSXvTWftX > 77+8xtWH6OlZ9ef0dWRyJtIzJ5MGtjVGpivQFq7aMBIqfxDU1uBV7wGRd3OIOEEn > a0kYGGYzmb96hX2Jn0wpUbS/ArBMuunJzFeMY5hdfxlM4q0e8Wj0LZOimfiKeew= > =2kgb > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-drivers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-drivers > To unsubscribe, send any mail to "freebsd-drivers-unsubscribe@freebsd.org" > >home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5252ECAB.8060706>