| From | Subject | Date |
|---|---|---|
| Marco Peereboom | [jordan@cvs.openbsd.org: ACPI new fulltask diff]
As promised.
This needs lots of testing so apply, test and reply to jordan and me please.
----- Forwarded message from Jordan Hargrave <jordan@cvs.openbsd.org> -----
Date: Wed, 15 Dec 2010 19:06:26 -0700 (MST)
From: Jordan Hargrave <jordan@cvs.openbsd.org>
To: marco@openbsd.org
Subject: ACPI new fulltask diff
This is a modified acpitask patch that adds all the power/sleep functionality to the task queue.
It gets rid of all the unecessary state variables in the acpi softc.
This works ...
| Dec 19, 9:14 am 2010 |
| Christopher Zimmermann | acpi and sysctl
Hi,
I've finally found some time to work on the fan control support for my
thinkpad.
But I'm having problems calling to acpiec_write() from sysctl or
timeout_set(9) context. (Assertion failure in acpiec_gpehandler()).
According to dev/acpi/acpiec.c:229 this function is meant to be called
only from "acpi thread context".
Now how am I supposed to talk to the acpi controller?
One solution would be to use the aml_register_notify(..., ACPIDEV_POLL)
callback mechanism already in use by the ...
| Dec 19, 8:12 am 2010 |
| Marco Peereboom | Re: acpi and sysctl
You are not supposed to talk directly to the ec device.
Jordan has a diff floating around for acpi tasklets. This really should
be the way to get this done. I'll forward the diff to tech with the
caveat that it isn't finalized yet.
I would prefer for this fan stuff to be automatic instead of by hand
| Dec 19, 9:12 am 2010 |
| EkonomiTürk Haber A ... | EkonomiTürk Haber Ajansı
TC<rkiye'nin ekonomi odaklD1 ilk ve tek haber ajansD1 EkonomiTC<rk yayD1na
baEladD1.
www.ekonomi-turk.com
D0Ete 19 AralD1k 2010 tarihli haberlerimizden bazD1larD1:
Suudiler DC<nyanD1n En YC<ksek BinasD1nD1 Yapacak!
Merkezi Suudi Arabistanbda bulunan KrallD1k Holding Eirketi'nin Cidde
kentine 20 milyar dolarlD1k
proje kapsamD1nda dC<nyanD1n en yC<ksek binasD1nD1 inEa edeceDi bildirildi.
ayrD1ntD1lar iC'in www.ekonomi-turk.com tD1klayD1nD1z.
TC<rkiye'nin Otomobil D0thalatD1 CD1D Gibi ...
| Dec 19, 7:04 am 2010 |
| Andreas Bartelt | Re: softraid(4) disks are of wrong size
I've only tested CRYPTO, but sr_meta_native_probe() seems to be used by
all disciplines.
Try newfs /dev/rsdXc where X is a virtual softraid(4) disk in order to
trigger the test case.
| Dec 19, 9:47 am 2010 |
| Otto Moerbeek | Re: softraid(4) disks are of wrong size
It is not agood idea, but since newfs write the last sector of a
partition (as a general consistency check in mkfs.c:203) it is a good
test to see if that last sector is indeed writable.
-Otto
| Dec 19, 10:16 am 2010 |
| Nick Holland | Re: softraid(4) disks are of wrong size
partition 'c' as a RAID partition? That's not good, is it?
Or am I missing something?
Nick.
| Dec 19, 9:51 am 2010 |
| Kenneth R Westerback | Re: softraid(4) disks are of wrong size
You should NEVER use 'c' partition. Amoung other things, it is
always set by the kernel to encompass the whole disk, everytime the
disklabel is read. If you restore to a different sized disk interesting
things might happen. I thought we also always set it to UNUSED, but
if not I will revisit that.
| Dec 19, 2:28 pm 2010 |
| Andreas Bartelt | softraid(4) disks are of wrong size
Hello,
I've noticed that the size of softraid(4) disks is one sector too large.
In the following description, the native disk is sd4c (which is of type
RAID), and the corresponding virtual softraid(4) disk will be sd5. I
will assume that sd5 is of discipline CRYPTO, but the problem should be
the same for all disciplines.
The size for sd5 gets eventually stored in struct sr_metadata as
sd_meta->ssdi.ssd_size in function sr_crypto_create
(dev/softraid_crypto.c). Its value gets initially ...
| Dec 19, 6:17 am 2010 |
| Ted Unangst | Re: softraid(4) disks are of wrong size
I can repro. Crypto raid.
sd0g: size 20986560 this is the real disk
sd1a: 20985952 offset 64
sd1c: 20986033
softraid reserves metaoffset + metasize + loadersize + bootblocks ==
528 sectors.
20986560 - 528 = 20986032
So that's one smaller than the fake disk thinks it is.
Lucky for me, my 'a' partition with the filesystem is only 20985952 +
64 = 20986016 sectors, so it didn't try to use the last few.
Numbers again, minus prefix:
Base disk: 560
Space after SR meta: 32
SR ...
| Dec 19, 3:32 pm 2010 |
| Marco Peereboom | Re: softraid(4) disks are of wrong size
I could swear we had the sizes right but I'll have another look at this.
What raid type did you test this with?
| Dec 19, 9:15 am 2010 |
| Jacob Meuser | Re: usb: add missing autoconf activate functions
yes, it's used to set the driver's dying flag. those are the most common
places a driver would be marked as dying. maybe also in an interrupt
currently it is just a wrapper for setting the dying flag in the driver's
usbd_device. maybe it will do other things, but probably not. the pupose
of setting the dying flag in the usbd_device is so that this flag can be
checked in generic stack functions, because the almost always have access
to the usbd_device. if there were just the dying flag ...
| Dec 18, 10:11 pm 2010 |
| Paul Irofti | Re: usb: add missing autoconf activate functions
About this interface, I looked around in the code and it seems to be
used mostly in activate functions and in failure cases inside attach.
My question is if its not better to make usbd_deactivate() a function
similar to an activate() one. That way we can just add something like
ubdi_activate in the cfattach instead of a wrapper to it in each driver.
I don't know what the plan is for usbd_deactivate thus what I'm
proposing might not make sense. Just a thought.
Otherwise it would sure get ...
| Dec 18, 8:02 pm 2010 |
| Paul Irofti | Dec 18, 8:06 pm 2010 |
| previous day | today | next day |
|---|---|---|
| December 18, 2010 | December 19, 2010 | December 20, 2010 |
