Hi guys, I successfully managed to survive the business trip and this damn hot weekend here in the north Germany, so I am back on track!
I have a few (not that nice to me) news to you all: 1. I have applied the patch, but the suspend mode (acpiconf -s 3) is not working; 2. I am still having problems with the battery. Actually when I put the pc to suspend and then try to wake it up, the screen stays black. I never had many, but I am running out of ideas! Cheers, Daniele. 2014-07-21 20:00 GMT+02:00 Anthony Jenkins <anthony.b.jenk...@att.net>: > Thanks all, the more feedback the better! > > John, yeah it was that & multibyte accesses (which I went ahead & > implemented... shouldn't hurt anything). > > Also I need to double-check that I allow atrtc unrestricted reads/writes, > but restrict ACPI to read-only accesses to the RTC registers. I'll have to > look into Ian's concerns about accessing those regs. I know old > implementations of the RTC use certain bits for NMI control & stuff. > > I'd have replied sooner, but managed to hose my GUI by updating > devel/dbus...rebuilding everything now :-( > > Anthony > Sent from Yahoo Mail on Android > <https://overview.mail.yahoo.com/mobile/?.src=Android> > > ------------------------------ > * From: * Ian Smith <smi...@nimnet.asn.au>; > * To: * John Baldwin <j...@baldwin.cx>; > * Cc: * <freebsd-acpi@freebsd.org>; Anthony Jenkins < > anthony.b.jenk...@att.net>; Daniele Mazzotti <kappe...@gmail.com>; > * Subject: * Re: ACPI support - Freebsd 10 on Sony Vaio VPCCA3C5E > * Sent: * Mon, Jul 21, 2014 5:39:56 PM > > On Mon, 21 Jul 2014 12:30:23 -0400, John Baldwin wrote: > > > On Thursday 17 July 2014 03:16:10 Ian Smith wrote: > > > On Wed, 16 Jul 2014 09:26:08 -0400, Anthony Jenkins wrote: > > > > On 07/16/2014 01:32, Daniele Mazzotti wrote: > > > >> Hi guys, thanks again for the support, but I am leaving for a > > > >> businesses trip and I will be forced to put this debug thing on > hold > > > >> for a while. I will be back on track next week. > > > > > > > > Bah... really wanted to figure out the patch problem. I suspect the > > > > file picked up some corruption somewhere between the email and your > > > > FreeBSD filesystem. Your OS version has the same revision of that > > > > source file as mine, so it should apply cleanly. If you feel like > > > > tinkering with it in your free time, I've posted the patch here: > > > > http://pastebin.com/P0B44u0c > > > > > > > > Good luck, > > > > Anthony > > > > > > Either by show raw and save, or by download, the patch has ^M lineends. > > > > > > Interesting, but I can't see atrtc.c being the right sort of place for > > > this, seems way out of scope. Couldn't you include its headers and use > > > functions rtcin() and writertc() from elsewhere in kernel, perhaps a > > > module living in the same hierarchy as acpi_ibm, acpi_asus and such, > > > that one could build and kldload if useful on a certain machine/s? > > > > I disagree, I think this is exactly the right place to do it. The CMOS > access > > on x86 boxes is going to be via the RTC, and the folks from Intel even > > indicated that the proper place to put the CMOS region handler is in the > > driver that claims the RTC PNP ID. The only pending question I was > aware of > > is that Anthony had asked the Intel guys a question about a return code, > but > > that barring that the patch was ready to go into the tree (and should > probably > > go in soon so it can make 10.1). > > > I agree :) Yes, as noted I was well under-researched, was myself out of > scope, and missed the basis of this entirely. I'm glad it's going ahead > despite my distractions .. > > cheers, Ian > > _______________________________________________ freebsd-acpi@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-acpi To unsubscribe, send any mail to "freebsd-acpi-unsubscr...@freebsd.org"