headers
Kenneth R Westerback | 1 Sep 2007 02:32
Favicon

Re: ACPI reboot method, testers required

On Fri, Aug 31, 2007 at 01:50:06PM -0600, Chris Kuethe wrote:
> On 8/29/07, Jonathan Gray <jsg <at> goblin.cx> wrote:
> > On Wed, Aug 29, 2007 at 08:16:09PM +0200, Karl Sj??dahl - dunceor wrote:
> > >
> > > I just tried it out but it doesn't seem to work for me:
> > > fadt hdr_rev: 1, reset reg_addr: 0xeeeeeeeeeeeeeeeee flags 0x84a5
> > > ACPI reboot method not supported
> >
> > This is expected behaviour, fadt hdr_rev = 1 does not support it.
> 
> fadt hdr_rev: 1, reset_reg.addr: 0x0 flags 0x4a5
> ACPI reboot method not supported
> 
> yet the machine still reboots. Gigabyte M61P-S3
> 
> -- 
> GDB has a 'break' feature; why doesn't it have 'fix' too?
> 

I have the same experience on my Dell D620, with different numbers.

fadt hdr_rev: 1, reset_reg.addr: 0xd19e8e0000000000 flags 0x82bd
ACPI reboot method not supported

.... Ken
Permalink | Reply | 1 comment |
headers
David H. Lynch Jr. | 1 Sep 2007 07:03
Picon

Sample Cardbus/PCMC(IA driver modules ?

    I am responsible for updating a port of the Pico Embedded 
development system host software for OpenBSD 3.9
    to current.

    If humanly possible I would like to be able to provide the Pico 
target Cardbus/PCMCIA drivers are a loadable module rather
    than as a patch to the OpenBSD kernel source.

    Much googling has resulting n a limited amount of resources for 
developing simple OpenBSD character device modules,
    but nothing about adapting them to Cardbus or PCMCIA (or in the near 
future express bus).

    I have experience with systems development on a number of platforms, 
but I am fairly new to OpenBSD.

    Pointers to more advanced driver/module development resources, even 
just general driver development resources
    would be greatly appreciated.

    I appologize if somehow in my searching I have missed something obvious.
Permalink | Reply | 4 comments |
headers
Jonathan Gray | 1 Sep 2007 10:55
Favicon

Re: Sample Cardbus/PCMC(IA driver modules ?

On Sat, Sep 01, 2007 at 01:03:52AM -0400, David H. Lynch Jr. wrote:
>    I am responsible for updating a port of the Pico Embedded development 
> system host software for OpenBSD 3.9
>    to current.
>
>    If humanly possible I would like to be able to provide the Pico target 
> Cardbus/PCMCIA drivers are a loadable module rather
>    than as a patch to the OpenBSD kernel source.
>
>    Much googling has resulting n a limited amount of resources for 
> developing simple OpenBSD character device modules,
>    but nothing about adapting them to Cardbus or PCMCIA (or in the near 
> future express bus).
>
>    I have experience with systems development on a number of platforms, but 
> I am fairly new to OpenBSD.
>      Pointers to more advanced driver/module development resources, even 
> just general driver development resources
>    would be greatly appreciated.
>
>    I appologize if somehow in my searching I have missed something obvious.

A very brief overview can be found here:
http://www.openbsd.org/papers/opencon06-drivers/index.html

Most commonly used kernel functions should be documented in section 9
man pages, and there is of course a large body of existing code in the tree
which does similiar things.  Any specific questions can be addressed to
tech <at> .
(Continue reading)

Permalink | Reply | 3 comments |
headers
Miod Vallat | 1 Sep 2007 14:13
Picon
Gravatar

Re: Cannot boot OpenBSD on landisk PX-EH from Seagate ST68022CF HDD

> Port landisk based on USL-5P platform that uses CF as bootable device. I
> try to use Seagate ST68022CF HDD with CF IDE interface to boot OpenBSD
> 4.2 current latest snapshot on compatible with USL-5P Plextor PX-EH
> platform, but nothing has turned out ....
> 
> Booting Seagate 8G microdrive with miniroot42.fs installation image:
> 
> SH IPL+g version 0.9, Copyright (C) 2000 Free Software Foundation,
> Inc.
> 
> This software comes with ABSOLUTELY NO WARRANTY; for details type `w'.
> This is free software, and you are welcome to redistribute it under
> certain conditions; type `l' for details.
> 
> 2002/09/09 Making.  2005/03/01 I-O DATA NSU Update for revB chip.
> 266:133:33 on base clock 22.22MHz and SDRAM 4 burst. ATA boot.
> 
> A-Card ATP865 ATA controller found.
> PCIC initialization done.
> MASTER:48bit LBA mode non support
> Disk drive detected: ST68022CF 3.01             4NX01SNP
> LBA: 00EE6B30
> DiskSize: 3705036800Byte
            ^^^^^^^^^^

This looks wrong for a 8GB drive.

> PIO MODE1
> A-Card ATP865 ATA controller found.
> > b
(Continue reading)

Permalink | Reply | 1 comment |
headers
David H. Lynch Jr. | 1 Sep 2007 14:53
Picon

Re: Sample Cardbus/PCMC(IA driver modules ?

Jonathan Gray wrote:
> A very brief overview can be found here:
> http://www.openbsd.org/papers/opencon06-drivers/index.html
>
> Most commonly used kernel functions should be documented in section 9
> man pages, and there is of course a large body of existing code in the tree
> which does similiar things.  Any specific questions can be addressed to
> tech <at> 
Thank you that provided a good start

Some questions that immediately come to mind:

How doe the load able module driver model relate to the in kernel model?
Can I just write a Cardbus/PCMCIA driver much as I would for in kernel
but build it as a module and expect that it will work ?

The driver am working with expects to use a small set of minor numbers
as well as ioctl's.

Am I correct that MAKEDEV seems to be the blessed way of creating the
/dev entries ?
If so how does MAKEDEV know about new drivers ?
After incorporating my driver I can mknod to create the /dev eentries,
but MAKEDEV does not seem to know about my driver.

Is there any in kernel scheme to automate the creation of /dev entries ?

Thanks.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Claudio Jeker | 1 Sep 2007 15:50

Re: Sample Cardbus/PCMC(IA driver modules ?

On Sat, Sep 01, 2007 at 08:53:24AM -0400, David H. Lynch Jr. wrote:
> Jonathan Gray wrote:
> >A very brief overview can be found here:
> >http://www.openbsd.org/papers/opencon06-drivers/index.html
> >
> >Most commonly used kernel functions should be documented in section 9
> >man pages, and there is of course a large body of existing code in the tree
> >which does similiar things.  Any specific questions can be addressed to
> >tech <at> 
> Thank you that provided a good start
> 
> Some questions that immediately come to mind:
> 
> How doe the load able module driver model relate to the in kernel model?
> Can I just write a Cardbus/PCMCIA driver much as I would for in kernel
> but build it as a module and expect that it will work ?
> 

OpenBSD does not support driver modules.

> The driver am working with expects to use a small set of minor numbers
> as well as ioctl's.
> 
> Am I correct that MAKEDEV seems to be the blessed way of creating the
> /dev entries ?

Yes.

> If so how does MAKEDEV know about new drivers ?
(Continue reading)

Permalink | Reply | 1 comment |
headers
David H. Lynch Jr. | 1 Sep 2007 21:35
Picon

Re: Sample Cardbus/PCMC(IA driver modules ?

Claudio Jeker wrote:
> On Sat, Sep 01, 2007 at 08:53:24AM -0400, David H. Lynch Jr. wrote:
>   
>> Jonathan Gray wrote:
>>     
>>> A very brief overview can be found here:
>>> http://www.openbsd.org/papers/opencon06-drivers/index.html
>>>
>>> Most commonly used kernel functions should be documented in section 9
>>> man pages, and there is of course a large body of existing code in the tree
>>> which does similiar things.  Any specific questions can be addressed to
>>> tech <at> 
>>>       
>> Thank you that provided a good start
>>
>> Some questions that immediately come to mind:
>>
>> How doe the load able module driver model relate to the in kernel model?
>> Can I just write a Cardbus/PCMCIA driver much as I would for in kernel
>> but build it as a module and expect that it will work ?
>>
>>     
>
> OpenBSD does not support driver modules.
>   

I am a bit gunshy about OpenBSD at the moment having misread the license 
and then misinterpreted it on misc <at> openbsd.org.

But googling OpenBSD Driver Modules, produces numerous hits and examples.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Martin Reindl | 1 Sep 2007 21:44

diff: aac(4) in -current

Can someone with an aac(4) please test this in -current?

Thanks.

Index: aac.c
===================================================================
RCS file: /cvs/src/sys/dev/ic/aac.c,v
retrieving revision 1.35
diff -u -p -r1.35 aac.c
--- aac.c	20 Mar 2007 10:30:32 -0000	1.35
+++ aac.c	1 Sep 2007 19:41:10 -0000
 <at>  <at>  -1592,7 +1592,7  <at>  <at>  aac_init(struct aac_softc *sc)
 	 * therefore 'assuming' that this value is in 16MB units (2^24).
 	 * Round up since the granularity is so high.
 	 */
-	ip->HostPhysMemPages = ctob(physmem) / AAC_PAGE_SIZE;
+	ip->HostPhysMemPages = ptoa(physmem) / AAC_PAGE_SIZE;
 	if (sc->flags & AAC_FLAGS_BROKEN_MEMMAP) {
 		ip->HostPhysMemPages =
 		    (ip->HostPhysMemPages + AAC_PAGE_SIZE) / AAC_PAGE_SIZE;
Permalink | Reply | 0 comments |
headers
Mike Belopuhov | 1 Sep 2007 21:24
Picon

[Patch] System lockup on D975XBX2

Hi tech,

Booting amd64 kernel on Intel D975XBX2 motherboard
with Core2 Duo E6550 (I know that I'm on my own here :^)
produces a permanent lockup executing i2c_scan routine.
Unfortunately DDB is not entered (and reset doesn't work
too) so there is no way to get a valid trace.

D975XBX2 features SMSC LPC47M182-NW chip completely
unsupported by OpenBSD (will try to support that shit
when they'll release docs one day ;)

ICHIIC_DEBUG flag revealed that system stops trying to init
addr 0x4c. Excluding this address from valid scan address
range makes the system boot fine:

OpenBSD 4.2-current (GENERIC) #0: Mon Sep  3 02:45:52 MSD 2007
    root <at> fort.crypt.org.ru:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 2128572416 (2029MB)
avail mem = 2055847936 (1960MB)
RTC BIOS diagnostic error 80<clock_battery>
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.4  <at>  0xe4380 (35 entries)
bios0: vendor Intel Corp. version "BX97520J.86A.2333.2006.1127.1450" date
11/27/2006
bios0: Intel Corporation D975XBX2
acpi at mainbus0 not configured
cpu0 at mainbus0: (uniprocessor)
cpu0: Intel(R) Core(TM)2 Duo CPU E6550  <at>  2.33GHz, 2333.37 MHz
cpu0:
(Continue reading)

Permalink | Reply | 2 comments |
headers
Devin Smith | 1 Sep 2007 23:12

Re: ACPI reboot method, testers required

> On Fri, Aug 31, 2007 at 01:50:06PM -0600, Chris Kuethe wrote:
>> On 8/29/07, Jonathan Gray <jsg <at> goblin.cx> wrote:
>> > On Wed, Aug 29, 2007 at 08:16:09PM +0200, Karl Sj??dahl - dunceor
>> wrote:
>> > >
>> > > I just tried it out but it doesn't seem to work for me:
>> > > fadt hdr_rev: 1, reset reg_addr: 0xeeeeeeeeeeeeeeeee flags 0x84a5
>> > > ACPI reboot method not supported
>> >
>> > This is expected behaviour, fadt hdr_rev = 1 does not support it.
>>
>> fadt hdr_rev: 1, reset_reg.addr: 0x0 flags 0x4a5
>> ACPI reboot method not supported
>>
>> yet the machine still reboots. Gigabyte M61P-S3
>>
>> --
>> GDB has a 'break' feature; why doesn't it have 'fix' too?
>>
>
> I have the same experience on my Dell D620, with different numbers.
>
> fadt hdr_rev: 1, reset_reg.addr: 0xd19e8e0000000000 flags 0x82bd
> ACPI reboot method not supported
>
> .... Ken

I'm not sure if you want more reports with fadt hdr_rev == 1, but I'm
reporting the same on a Compaq Presario 2103us:
(Continue reading)

Permalink | Reply | 0 comments |

Gmane