From devnull at illumos.org  Thu Nov  1 08:35:51 2012
From: devnull at illumos.org (illumos project)
Date: Thu, 1 Nov 2012 08:35:51 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #2029] gtkam crashing
References: <redmine.issue-2029.20120124194902@illumos.org>
Message-ID: <redmine.journal-8461.20121101083550@illumos.org>


Issue #2029 has been updated by r a.

File building-libgphoto2-2.5.0.txt added
Assignee changed from OI Userland to OI illumos
Target version set to oi_151_stable

Tried to build libgphoto2-2.5.0 but it complained about the libusb library, as it requires a version of libusb that is version 1.0.0 or later. Checking the version information in package manager, the version shipped with OpenIndiana is version 0.1.8. The current release of libusb from http://www.libusb.org/ is version 1.0.9.

Can base version of libusb be upgraded to v1.0.9


----------------------------------------
Bug #2029: gtkam crashing
https://www.illumos.org/issues/2029

Author: r a
Status: Feedback
Priority: Normal
Assignee: OI illumos
Category: 
Target version: oi_151_stable
Difficulty: Medium
Tags: gtkam


Late time I used gtkam on OpenIndiana to download photos from my Nikon L20 digital camera it worked perfectly and had been working for months. However when I tried to download photos today using gtkam, it crashes as it attempts to load  /usr/lib/libgphoto2/2.4.9.1
See the attached truss of gtkam as it crashes.



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Thu Nov  1 08:43:50 2012
From: devnull at illumos.org (illumos project)
Date: Thu, 1 Nov 2012 08:43:50 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #2029] gtkam crashing
References: <redmine.issue-2029.20120124194902@illumos.org>
Message-ID: <redmine.journal-8462.20121101084350@illumos.org>


Issue #2029 has been updated by r a.


The previous post is incorrect as OpenIndiana is using http://sourceforge.net/apps/trac/openusb which is MT-safe. However the current version is currently v1.1.7 which is still more up recent that the current version.

----------------------------------------
Bug #2029: gtkam crashing
https://www.illumos.org/issues/2029

Author: r a
Status: Feedback
Priority: Normal
Assignee: OI illumos
Category: 
Target version: oi_151_stable
Difficulty: Medium
Tags: gtkam


Late time I used gtkam on OpenIndiana to download photos from my Nikon L20 digital camera it worked perfectly and had been working for months. However when I tried to download photos today using gtkam, it crashes as it attempts to load  /usr/lib/libgphoto2/2.4.9.1
See the attached truss of gtkam as it crashes.



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From pavel.zakharov at mail.mcgill.ca  Thu Nov  1 14:32:05 2012
From: pavel.zakharov at mail.mcgill.ca (Pavel Zakharov)
Date: Thu, 1 Nov 2012 14:32:05 +0000
Subject: [Illumos-team] 64-Bit PCI space
Message-ID: <0A3710D0584AEE40B1DDDD5654D0B307099D15@EXMBX2010-1.campus.MCGILL.CA>

Hello,

I've been trying a new feature on my BIOS that allows to memory map PCI device registers to spaces above 4G.

However, when I booted in Solaris, it failed to load some devices, and pci_boot also reported:
"unsupported 64-bit prefetch memory on pci-pci bridge [%d/%d/%d]" (copy pasted that line from pci_boot.c)
Digging further I also found some comments in npe.c in a register mapping function:
case PCI_ADDR_MEM64:
/*
* We can't handle 64-bit devices that are mapped above
* 4G or that are larger than 4G.
*/

I am in the process of rewriting the driver code right now, but I am wondering how deep will I have to go or if a fix already exists in OpenIndiana.
If you are wondering why I need all this, it is because I have a device that requires a very large space of prefetchable memory (>4G) and I need those BIOS settings to make it boot.

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/illumos-team/attachments/20121101/1116f894/attachment-0001.html>

From garrett at damore.org  Thu Nov  1 15:00:08 2012
From: garrett at damore.org (Garrett D'Amore)
Date: Thu, 1 Nov 2012 08:00:08 -0700
Subject: [Illumos-team] 64-Bit PCI space
In-Reply-To: <0A3710D0584AEE40B1DDDD5654D0B307099D15@EXMBX2010-1.campus.MCGILL.CA>
References: <0A3710D0584AEE40B1DDDD5654D0B307099D15@EXMBX2010-1.campus.MCGILL.CA>
Message-ID: <231A2D30-27D8-42BC-88A8-A70DCE375BA2@damore.org>

I suspect this rabbit hole goes pretty deep.  Obviously, it won't be possible to use this device in a 32-bit kernel, either.  You'd want to examine the entire PCI stack, and possibly also the iommu code for this stuff.  (I doubt you can use this device with an iommu, also.)

	- Garrett

On Nov 1, 2012, at 7:32 AM, Pavel Zakharov <pavel.zakharov at mail.mcgill.ca> wrote:

> Hello,
> 
> I've been trying a new feature on my BIOS that allows to memory map PCI device registers to spaces above 4G.
> 
> However, when I booted in Solaris, it failed to load some devices, and pci_boot also reported:
> "unsupported 64-bit prefetch memory on pci-pci bridge [%d/%d/%d]" (copy pasted that line from pci_boot.c)
> Digging further I also found some comments in npe.c in a register mapping function:
> case PCI_ADDR_MEM64:
> /*
> * We can't handle 64-bit devices that are mapped above
> * 4G or that are larger than 4G.
> */
> 
> I am in the process of rewriting the driver code right now, but I am wondering how deep will I have to go or if a fix already exists in OpenIndiana.
> If you are wondering why I need all this, it is because I have a device that requires a very large space of prefetchable memory (>4G) and I need those BIOS settings to make it boot.
> 
> Thanks
> _______________________________________________
> Illumos-team mailing list
> Illumos-team at openindiana.org
> http://openindiana.org/mailman/listinfo/illumos-team

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/illumos-team/attachments/20121101/854a11f8/attachment.html>

From pavel.zakharov at mail.mcgill.ca  Thu Nov  1 15:36:26 2012
From: pavel.zakharov at mail.mcgill.ca (Pavel Zakharov)
Date: Thu, 1 Nov 2012 15:36:26 +0000
Subject: [Illumos-team] 64-Bit PCI space
In-Reply-To: <231A2D30-27D8-42BC-88A8-A70DCE375BA2@damore.org>
References: <0A3710D0584AEE40B1DDDD5654D0B307099D15@EXMBX2010-1.campus.MCGILL.CA>,
	<231A2D30-27D8-42BC-88A8-A70DCE375BA2@damore.org>
Message-ID: <0A3710D0584AEE40B1DDDD5654D0B30709B12D@EXMBX2010-1.campus.MCGILL.CA>

[ccing maillist]
Thanks Garrett,
That's precisely what I'm doing right now.
In most of the places, the fixes I need to do is just removing hardcoded restrictions and changing uint to uint64.
There's one structure however, 'struct regspec', which seems to require more care since it is integrated in a ddi_map_obj_t structure and is passed around quite a lot.

Pavel
________________________________
From: Garrett D'Amore [garrett.damore at gmail.com] on behalf of Garrett D'Amore [garrett at damore.org]
Sent: Thursday, November 01, 2012 11:00 AM
To: Pavel Zakharov
Cc: illumos-team at openindiana.org
Subject: Re: [Illumos-team] 64-Bit PCI space

I suspect this rabbit hole goes pretty deep.  Obviously, it won't be possible to use this device in a 32-bit kernel, either.  You'd want to examine the entire PCI stack, and possibly also the iommu code for this stuff.  (I doubt you can use this device with an iommu, also.)

- Garrett

On Nov 1, 2012, at 7:32 AM, Pavel Zakharov <pavel.zakharov at mail.mcgill.ca<mailto:pavel.zakharov at mail.mcgill.ca>> wrote:

Hello,

I've been trying a new feature on my BIOS that allows to memory map PCI device registers to spaces above 4G.

However, when I booted in Solaris, it failed to load some devices, and pci_boot also reported:
"unsupported 64-bit prefetch memory on pci-pci bridge [%d/%d/%d]" (copy pasted that line from pci_boot.c)
Digging further I also found some comments in npe.c in a register mapping function:
case PCI_ADDR_MEM64:
/*
* We can't handle 64-bit devices that are mapped above
* 4G or that are larger than 4G.
*/

I am in the process of rewriting the driver code right now, but I am wondering how deep will I have to go or if a fix already exists in OpenIndiana.
If you are wondering why I need all this, it is because I have a device that requires a very large space of prefetchable memory (>4G) and I need those BIOS settings to make it boot.

Thanks
_______________________________________________
Illumos-team mailing list
Illumos-team at openindiana.org<mailto:Illumos-team at openindiana.org>
http://openindiana.org/mailman/listinfo/illumos-team

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openindiana.org/pipermail/illumos-team/attachments/20121101/224e0566/attachment.html>

From devnull at illumos.org  Sat Nov 10 00:16:39 2012
From: devnull at illumos.org (illumos project)
Date: Sat, 10 Nov 2012 00:16:39 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Bug #3350] Supported NIC
	not recognized by Install CD
References: <redmine.issue-3350.20121109173004@illumos.org>
Message-ID: <redmine.journal-8526.20121110001639@illumos.org>


Issue #3350 has been updated by Ken Mays.

Assignee set to OI illumos
Target version deleted (oi_151_stable)


----------------------------------------
Bug #3350: Supported NIC not recognized by Install CD
https://www.illumos.org/issues/3350

Author: Lipe C
Status: New
Priority: High
Assignee: OI illumos
Category: Drivers
Target version: 
Difficulty: Medium
Tags: needs-triage


Hi mates,

According to http://wiki.openindiana.org/oi/Ethernet+Networking the Broadcom BCM5720 is supported by OpenIndiana,
but i cannot get it recognized by the Install CD. Ive tried to download the solaris drivers for this board direcly from Broadcom
website but cannot get it installed neither automatically or by option 2.

Any ideas? Ive found some issues related to these 'bge drivers' on Solaris but most of them were 1 year old, related to version 148.

The BCM5720 is a dual gigabit part of a Dell T420 (Tower), most knew as R420 (Rack version).

Best regards


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Thu Nov 15 21:54:16 2012
From: devnull at illumos.org (illumos project)
Date: Thu, 15 Nov 2012 21:54:16 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Feature #3365] (New) bge
	driver device detection improvement
Message-ID: <redmine.issue-3365.20121115215416@illumos.org>


Issue #3365 has been reported by Ken Mays.

----------------------------------------
Feature #3365: bge driver device detection improvement
https://www.illumos.org/issues/3365

Author: Ken Mays
Status: New
Priority: Normal
Assignee: OI illumos
Category: Drivers
Target version: 
Difficulty: Bite-size
Tags: bge


Update the bge driver to fully support Broadcom 57xx devices:

BCM5714, 5715, 5717, 5718, 5719, 5720, 5721, 5722, 5723, 5780 


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


From devnull at illumos.org  Thu Nov 15 21:58:29 2012
From: devnull at illumos.org (illumos project)
Date: Thu, 15 Nov 2012 21:58:29 +0000
Subject: [Illumos-team] [OpenIndiana Distribution - Feature #3365] bge
	driver device detection improvement
References: <redmine.issue-3365.20121115215416@illumos.org>
Message-ID: <redmine.journal-8556.20121115215829@illumos.org>


Issue #3365 has been updated by Ken Mays.


SUNWbge driver should at least support: BCM5700, 5701, 5702, 5703, 5704, 5705, 5714, 5715, 5717, 5718, 5719, 5720, 5721, 5722, 5723, 5751, 5753, 5754, 5755, 5756, 5780, 5782, 5786, 5787, 5788, 5789, 5901, 5906
----------------------------------------
Feature #3365: bge driver device detection improvement
https://www.illumos.org/issues/3365

Author: Ken Mays
Status: New
Priority: Normal
Assignee: OI illumos
Category: Drivers
Target version: 
Difficulty: Bite-size
Tags: bge


Update the bge driver to fully support Broadcom 57xx devices:

BCM5714, 5715, 5717, 5718, 5719, 5720, 5721, 5722, 5723, 5780 


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account


