headers
Christopher Johnson | 1 Jun 2003 01:03
Picon

Re: Native JDK with libthr/libkse

On Sat, 31 May 2003, Dag-Erling Smorgrav wrote:

> Daniel Eischen <eischen <at> pcnet.com> writes:
> > What are the above error messages?  Sorry, I've never been able to
> > build native java for FreeBSD.
> 
> # cd /usr/ports/java/jdk13
> # make install clean
> 
> DES
> 

I disagree.  I recently built jdk13 on Friday and it died on me,
complaining about needing npapi.h.  The build instructions did
mention downloading the Sun SDK source and eyesbeyond patchset,
but did not mention the Qt Netscape Plugin Extension.

(I am not a Java programmer, I just like having the Java plugin
for Mozilla.  I am using 5.1-BETA and mozilla-devel (1.4b).)

The fix:
1) Go to
http://wp.netscape.com/comprod/development_partners/plugin_api/index.html.

2) Navigate to the "Unix LiveConnect/Plug-in SDK", and download
the Plugin SDK.  As of today, you can download it directly from:
ftp://ftp.netscape.com/pub/sdk/plugin/unix/unix-sdk-3.0b5.tar.Z

3) Extract the headers to a place where the build can find them
(I put them in /usr/X11R6/include, I suspect there's a more
(Continue reading)

Permalink | Reply | 9 comments |
headers
Dag-Erling Smorgrav | 1 Jun 2003 01:15

Re: Native JDK with libthr/libkse

Christopher Johnson <cjohnson <at> wcug.wwu.edu> writes:
> On Sat, 31 May 2003, Dag-Erling Smorgrav wrote:
> > Daniel Eischen <eischen <at> pcnet.com> writes:
> > > What are the above error messages?  Sorry, I've never been able to
> > > build native java for FreeBSD.
> > # cd /usr/ports/java/jdk13
> > # make install clean
> I disagree.  I recently built jdk13 on Friday and it died on me,
> complaining about needing npapi.h.  The build instructions did
> mention downloading the Sun SDK source and eyesbeyond patchset,
> but did not mention the Qt Netscape Plugin Extension.
> [...]

I just built jdk13 a couple of days ago.  No problem whatsoever.  You
guys must have rotten karma or something.

DES
--

-- 
Dag-Erling Smorgrav - des <at> ofug.org
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 7 comments |
headers
M. Warner Losh | 1 Jun 2003 01:42

Re: viapropm doesnt like sys/dev/pci.c rev 1.214

In message: <20030531210600.GA670 <at> tombstone.localnet.gomerbud.com>
            "David P. Reese Jr." <daver <at> gomerbud.com> writes:
: Is it my chipset's fault for not reading back the correct register value?
: The board is a SOYO K7VTAPRO-2AA6.  What other info would be helpful in
: this situation?

It appears that there's some non-zero latency between when we command
the bits to change and they really change.  A number of people have
reported this, but I'm not what the right way to fix it is.

Warner
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
Dag-Erling Smorgrav | 1 Jun 2003 01:52

Re: viapropm doesnt like sys/dev/pci.c rev 1.214

"David P. Reese Jr." <daver <at> gomerbud.com> writes:
> In rev 1.214 of sys/dev/pci/pci.c, we have started checking if a
> pci_set_command_bit() was successful with a subsequent PCI_READ_CONFIG
> and comparing the results.  For some odd reason, this doesnt work when
> my viapropm tries to attach.

viapropm is seriously broken for other reasons and needs professional
help.

>         pci_set_command_bit(dev, child, bit);
>         command = PCI_READ_CONFIG(dev, child, PCIR_COMMAND, 2);
>         if (command & bit)
>                 return (0);

It should allow the register to "settle" between write and read, which
may take some time (see chipset docs for timing details).  DELAY(1000)
should be OK in an attach function.

DES
--

-- 
Dag-Erling Smorgrav - des <at> ofug.org
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 9 comments |
headers
Scott Long | 1 Jun 2003 01:57

Re: 5.1-RELEASE TODO

Luigi Rizzo wrote:
> On Sat, May 31, 2003 at 09:00:16AM -0400, Robert Watson wrote:
> 
>>This is an automated bi-daily mailing of the FreeBSD 5.1 open issues list.
>>The live version of this list is available at:
>>
>>    http://www.FreeBSD.org/releases/5.1R/todo.html
>>
>>Automated mailing of this list will continue through the release of
>>FreeBSD 5.1.
>>
>>
>>                            FreeBSD 5.1 Open Issues
>>
>>                                  Open Issues
>>
>>   This is a list of open issues that need to be resolved for FreeBSD 5.1. If
>>   you have any updates for this list, please e-mail re <at> FreeBSD.org.
>>
>>  Must Resolve Issues for 5.1-RELEASE
>>
>>   +------------------------------------------------------------------------+
>>   |      Issue       |   Status    | Responsible |       Description       |
>>   |------------------+-------------+-------------+-------------------------|
>>   |                  |             |             | There are reports of    |
>>   | ipfw/ipfw2       |             |             | alignment problems with |
>>   | alignment issues | In progress | Luigi Rizzo | ipfw and/or ipfw2 on    |
>>   | on alpha/sparc64 |             |             | 64-bit platforms        |
>>   |                  |             |             | (specifically alpha and |
>>   |                  |             |             | sparc64).               |
(Continue reading)

Permalink | Reply | 8 comments |
headers
Robert Watson | 1 Jun 2003 02:18
Picon
Favicon

Re: 5.1-RELEASE TODO

On Sat, 31 May 2003, Scott Long wrote:

> It's been a matter of not having enough time, nothing more.  I *will*
> address this one way or another before the release.  I apologize for
> taking so long. 

Ditto, here, unfortunately.  I managed to hose my sparc64 box a couple of
weeks ago trying to upgrade it to run precisely these tests, but haven't
had time to figure out how to recover it.

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert <at> fledge.watson.org      Network Associates Laboratories

_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 6 comments |
headers
Bruce A. Mah | 1 Jun 2003 02:20
X-Face
Picon
Favicon

Re: 5.1-RELEASE TODO

If memory serves me right, Scott Long wrote:

> It's been a matter of not having enough time, nothing more.  I *will*
> address this one way or another before the release.  I apologize for
> taking so long.

Scott, you're hardly the only person with the ability to test this
problem.  In fact, you're not even personally affected by this.  So
don't be too hard on yourself.

Luigi, thanks for coming up with a patch...can't remember if I said that
before.  I'm mystified as to why nobody's stepped forward to help you
test it.  

Bruce.
Permalink | Reply | 0 comments |
headers
Bernd Walter | 1 Jun 2003 02:22
Picon

Re: 5.1-RELEASE TODO

On Sat, May 31, 2003 at 02:24:59PM -0700, Luigi Rizzo wrote:
> On Sat, May 31, 2003 at 09:00:16AM -0400, Robert Watson wrote:
> >    +------------------------------------------------------------------------+
> >    |      Issue       |   Status    | Responsible |       Description       |
> >    |------------------+-------------+-------------+-------------------------|
> >    |                  |             |             | There are reports of    |
> >    | ipfw/ipfw2       |             |             | alignment problems with |
> >    | alignment issues | In progress | Luigi Rizzo | ipfw and/or ipfw2 on    |
> >    | on alpha/sparc64 |             |             | 64-bit platforms        |
> >    |                  |             |             | (specifically alpha and |
> >    |                  |             |             | sparc64).               |
> >    +------------------------------------------------------------------------+
> 
> i posted patches and a detailed description for this item
> 3 weeks ago to re <at>  and then the same was forwarded a couple of weeks
> ago to the relevant lists (ipfw, sparc64, alpha) and got no 
> useful feedback (in detail, two message: one 'cannot apply the patch',
> the other one 'it dumps core' without further details).

A gdb stacktrace is much more than "without further details".
It happened inside bcopy.
I asumed that the stacktrace including the sourceline calling bcopy
would be enough.
If you need more then you should say so - I can't guess.

> As i do not have access to these platforms, all i can do is provide
> code and make sure that it compiles (which i did, using a cross-build),
> but for running it (part of the problem involves the kernel) i need
> someone with root&console access to test them.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Conrad Sabatier | 1 Jun 2003 02:26
Picon
Gravatar

viapm attach failure (was Re: loader vs PCI)


On 20-May-2003 Julian Elischer wrote:
> 
> Is there any capability in the loader to do such things as get/set a PCI
> config space register?
> 
> Looking at the  man page I'd say not, but there is mention of
> some PNP capacity (though not currently working).
> 
> 
> Reason..
> 
> ASUS disable the SMBus on their new mother boards and have no BIOS entry
> to enable it, but it can be enabled from the PCI config regs. Without
> it you can not easily read the voltages, temperatures and Fan speeds.
> 
> You can use pciconf to enable it but by then it's too late
> for the ichsmb(4) driver to find it. The only other answer is to 
> enable it, and then kldload the ichsmb module, but the best answer
> would be to enable it from the loader so that it shows up on the PCI
> bus during normal boot.
> 
> (ASUS need to get a clue on this.. a BIOS option would be real nice..)

I have a related problem.  I'm trying to get the viapm (viapropm0) device
to attach properly at boot, but to no avail.  The device is recognized, but
I always get the following:

smbios0: <System Management BIOS> at iomem 0xf7a20-0xf7a3e on motherboard
smbios0: Version: 2.03, Revision: 1.08
(Continue reading)

Permalink | Reply | 0 comments |
headers
Luigi Rizzo | 1 Jun 2003 02:39

Re: 5.1-RELEASE TODO

On Sat, May 31, 2003 at 08:18:10PM -0400, Robert Watson wrote:
> On Sat, 31 May 2003, Scott Long wrote:
> 
> > It's been a matter of not having enough time, nothing more.  I *will*
> > address this one way or another before the release.  I apologize for
> > taking so long. 
> 
> Ditto, here, unfortunately.  I managed to hose my sparc64 box a couple of
> weeks ago trying to upgrade it to run precisely these tests, but haven't
> had time to figure out how to recover it.

no need to apologize, as i said i am perfectly fine with people not
having time, and surely the RE team is taken by more urgent issues
these days. My mail was meant just as a reminder, nothing more.

As for the patch i posted: i don't claim it to be perfect, it might
contain some trivial bug such as passing the wrong variable to a
function, but hopefully those are things that a programmer who has
access to the box can find out and fix very quickly.

	cheers
	luigi
_______________________________________________
freebsd-current <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe <at> freebsd.org"
Permalink | Reply | 5 comments |

Gmane