where did you get the devg-poulsbo from?

Just as an experiment,
restart your computer and after you select an image, hit the space bar for 
extra boot options, hit F6 two or three times and hit enter.
Take note of the last message before booting halts.
Also, on another startup, enable a debug shell, and when boot halts and kicks 
you to the shell, set your path and run "get_hw_info" and attach a copy of 
the results here (you can use a usb key to get the results onto a comp. with 
net access).
I'm looking forward to hearing the results of these.
Cheers,
-Aaron
On Monday 13 October 2008 09:58:03 Maurizio Rossi wrote:
> I'm testing 6.4.0 on a Kontron system based on Intel Atom processor.
> This board has the following devices:
> network adapter vid=0x8086 did=0x10d3
> graphics adapter vid=0x8086 did=0x8108
>
> I don't konw if what I'm reporting is a bug or not.
>
> The "devnp-i82544.so" is unable to manage the network controllers i.e.
> refuse to startup. The "devn-i82544.so" from QNX6.3.2 running on 6.4.0
> works fine.
> In both cases the vid/did parameters are passed to the driver.
>
> Adding the "devg-poulsbo.so" driver to "/etc/system/enum/devices/graphics"
> cause the photon environment not to startup. Maybe this driver does not
> work with Photon?
>
> Regards,
> Maurizio Rossi
>
>
>
> _______________________________________________
> QNX Software Development Platform 6.4.0 Pre-Release
> http://community.qnx.com/sf/go/post14911

Hi Maurizio:
   One of the things that came up with the devnp version of the driver
is that we have some code in the devn driver which we don't know if we
can put in the public domain.  We ended up taking code from FreeBSD to
do the EEPROM reading so it's possible that the devn driver may support
more devices than the devnp (although I thought that we were the same).
Could you tell me what the output from sloginfo reports when using the
devnp driver?

	You'll also find that the devn driver (built for 6.4.0) is still
included in the packaging for exactly this reason, so you can given that
one a try as well.

	Thanks
		Robert.

-----Original Message-----
From: Maurizio Rossi [mailto:community-noreply@qnx.com] 
Sent: Monday, October 13, 2008 9:58 AM
To: sdp640prerelease-community
Subject: QNX6.4.0 M8 Build on Atom

I'm testing 6.4.0 on a Kontron system based on Intel Atom processor.
This board has the following devices:
network adapter vid=0x8086 did=0x10d3
graphics adapter vid=0x8086 did=0x8108

I don't konw if what I'm reporting is a bug or not.

The "devnp-i82544.so" is unable to manage the network controllers i.e.
refuse to startup.
The "devn-i82544.so" from QNX6.3.2 running on 6.4.0 works fine.
In both cases the vid/did parameters are passed to the driver.

Adding the "devg-poulsbo.so" driver to
"/etc/system/enum/devices/graphics" cause the photon environment not to
startup.
Maybe this driver does not work with Photon?

Regards,
Maurizio Rossi



_______________________________________________
QNX Software Development Platform 6.4.0 Pre-Release
http://community.qnx.com/sf/go/post14911

we ran into this recently, modify the enmerator file to force the poulsbo driver to start in 800x600 ... notice -g 
option

device(pci, ven=8086, dev=8108)                         # SGX/Poulsbo 
  start/wait( dispconf -i "0x$(ven),0x$(dev),$(index)" -d poulsbo -g "xres=800,yres=600" ) 

  requires/wait( $(IODISPLAY_CMD), ) 
  mount(-Tio-display "vid=0x$(ven),did=0x$(dev),deviceindex=$(index)" ) 


the driver is reporting it supports all generic modes, and maybe it should, but currently all modes do not work, only 
800x600, 1024x768, and 1280x1024