Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Jul 2014 11:00:55 -0700
From:      Anthony Jenkins <anthony.b.jenkins@att.net>
To:        Ian Smith <smithi@nimnet.asn.au>, John Baldwin <john@baldwin.cx>
Cc:        Anthony Jenkins <Anthony.B.Jenkins@att.net>, "freebsd-acpi@freebsd.org" <freebsd-acpi@freebsd.org>, Daniele Mazzotti <kappei84@gmail.com>
Subject:   Re: ACPI support - Freebsd 10 on Sony Vaio VPCCA3C5E
Message-ID:  <1405965655.15937.YahooMailAndroidMobile@web181606.mail.ne1.yahoo.com>
In-Reply-To: <20140722033156.E8638@sola.nimnet.asn.au>

next in thread | previous in thread | raw e-mail | index | archive | help
Thanks all,=A0 the more feedback the better! =0A=0AJohn, yeah it was that &=
 multibyte accesses (which I went ahead & implemented... shouldn't hurt any=
thing).=0A=0AAlso I need to double-check that I allow atrtc unrestricted re=
ads/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. =0A=
=0AI'd have replied sooner, but managed to hose my GUI by updating devel/db=
us...rebuilding everything now :-( =0A=0AAnthony=0ASent from Yahoo Mail on =
Android=0A=0A
From owner-freebsd-acpi@FreeBSD.ORG  Mon Jul 21 19:47:53 2014
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
Delivered-To: freebsd-acpi@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 76243BC
 for <freebsd-acpi@freebsd.org>; Mon, 21 Jul 2014 19:47:53 +0000 (UTC)
Received: from mail-yh0-x22f.google.com (mail-yh0-x22f.google.com
 [IPv6:2607:f8b0:4002:c01::22f])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 3706C2C55
 for <freebsd-acpi@freebsd.org>; Mon, 21 Jul 2014 19:47:53 +0000 (UTC)
Received: by mail-yh0-f47.google.com with SMTP id f10so4384757yha.34
 for <freebsd-acpi@freebsd.org>; Mon, 21 Jul 2014 12:47:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=6jzBEMco24/fnEGKZLbXPS4PlDg8NJPbrURPf3pTyhI=;
 b=fkzy4bYYfUoKZHppAcJVRtmAeYXZ6IFELgvE+QTpX79TC/PJiRfny6ngAUd+pMvItQ
 IKUsJxptSQAaoqzOiFxbylJO0YelnLHKBI9fPqdgOzKSUSGHga5loFhSFWj99re3+WDr
 s4UNCdgzEf0/9u6zbvt89tXrPFfICO3yb5XMzkkz2a5PzJtJHdOKORiPK3ysNzdlPLci
 Tffy9SpJEY9dUahLbcyU7MMS3ivOJtqGxOjUYyAM91pcbxAEyhNRnRMmm74woJesls1j
 7dsK6ENlCSD1qKPlUW67ghpudODEWrDsFlDcV09CBr5yn59w2u3yIJQdaIF1A8/fiwEE
 Ax7A==
MIME-Version: 1.0
X-Received: by 10.236.160.67 with SMTP id t43mr43687526yhk.11.1405972072234;
 Mon, 21 Jul 2014 12:47:52 -0700 (PDT)
Received: by 10.170.210.86 with HTTP; Mon, 21 Jul 2014 12:47:52 -0700 (PDT)
In-Reply-To: <1405965655.15937.YahooMailAndroidMobile@web181606.mail.ne1.yahoo.com>
References: <20140722033156.E8638@sola.nimnet.asn.au>
 <1405965655.15937.YahooMailAndroidMobile@web181606.mail.ne1.yahoo.com>
Date: Mon, 21 Jul 2014 21:47:52 +0200
Message-ID: <CAC=ypSV1w0V0Vg2N0fZQK-VOh5Pzm3t7Cnch9xT=HYMjxcvqtw@mail.gmail.com>
Subject: Re: ACPI support - Freebsd 10 on Sony Vaio VPCCA3C5E
From: Daniele Mazzotti <kappei84@gmail.com>
To: Anthony Jenkins <anthony.b.jenkins@att.net>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18
Cc: John Baldwin <john@baldwin.cx>,
 "freebsd-acpi@freebsd.org" <freebsd-acpi@freebsd.org>,
 Ian Smith <smithi@nimnet.asn.au>
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-acpi>,
 <mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi/>;
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
 <mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jul 2014 19:47:53 -0000

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.jenkins@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 <smithi@nimnet.asn.au>;
> * To: * John Baldwin <john@baldwin.cx>;
> * Cc: * <freebsd-acpi@freebsd.org>; Anthony Jenkins <
> Anthony.B.Jenkins@att.net>; Daniele Mazzotti <kappei84@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
>
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1405965655.15937.YahooMailAndroidMobile>