The link points to a commercial s/w. Is there interest in getting a free
driver for this? Any T40 sensor enabled laptop users run freebsd?
thanks
-kamal
On 6/30/06, Julian Elischer <[EMAIL PROTECTED]> wrote:
Anish Mistry wrote:
>On Friday 30 June 2006 04:49, Kamal R. Prasad wrote:
>
>
>>Hello
In the last episode (Jul 01), Jean-Marc Lienher said:
> After a (too?) quick look at the FreeBSD source code, I've seen that
> the GNU compiler toolchain was used to compile the kernel and other
> part of the OS.
>
> I would like to know if there is another compiler toolchain (C
> compiler, assemb
Kip Macy writes:
| WOW THATS GREAT DOUG! \0/ - it didn't work for me.
This was with the last patched driver for vmware 2. I'm not sure if
it every made it into the port.
http://www.mindspring.com/~vsilyaev/vmware/files/changes
28 Jan 01 Version 0.99-1-0.22
Support for multiple vmware
On Saturday 01 July 2006 10:26, Jean-Marc Lienher wrote:
> Hi all,
G'Day,
> I'm new to FreeBSD, I was using Linux since 1997.
> But I decided to switch to the Daemon and leave the Penguin on
> his Iceberg.
> (Yes, for those who are reading the hidden e-mail headers,
> I'm also using MS-Windows :-)
On Sat, Jul 01, 2006 at 02:26:35AM +0200, Jean-Marc Lienher wrote:
>
> After a (too?) quick look at the FreeBSD source code, I've seen that
> the GNU compiler toolchain was used to compile the kernel and other
> part of the OS.
>
> I would like to know if there is another compiler toolchain
> (C
WOW THATS GREAT DOUG! \0/ - it didn't work for me.
-Kip
On 6/30/06, Doug Ambrisko <[EMAIL PROTECTED]> wrote:
Kip Macy writes:
| IIRC lack of per instance cdevs also limits Freebsd to one vmware instance.
Really? Don't tell my vmware multiple instances! I used to run 10 on
one FreeBSD host.
D
Hi all,
I'm new to FreeBSD, I was using Linux since 1997.
But I decided to switch to the Daemon and leave the Penguin on
his Iceberg.
(Yes, for those who are reading the hidden e-mail headers,
I'm also using MS-Windows :-)
After a (too?) quick look at the FreeBSD source code, I've seen that
the G
Kip Macy writes:
| IIRC lack of per instance cdevs also limits Freebsd to one vmware instance.
Really? Don't tell my vmware multiple instances! I used to run 10 on
one FreeBSD host.
Doug A.
___
freebsd-hackers@freebsd.org mailing list
http://lists.fre
On Fri, 2006-Jun-30 20:29:28 +0200, Hans Petter Selasky wrote:
>I sometimes see that the USB driver is unable to allocate contiguous memory
>for itself. For example I noticed that FreeBSD was unable to allocate
>350kbytes of contiguous memory after that I had run "konqueror", the KDE web
>browse
FreeBSD's strategy for doing page coloring makes contiguous memory
allocation much past boot quite difficult. This will change when
generalized superpage support is brought in (I hope in the near
future).
-Kip
On 6/30/06, Hans Petter Selasky <[EMAIL PROTECTED]> wrote:
Hi,
I sometimes see tha
Anish Mistry wrote:
On Friday 30 June 2006 04:49, Kamal R. Prasad wrote:
Hello,
[...]
http://shapeshifter.se/articles/upek_touchchip_freebsd/
I'm impressed
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/
Hi,
I sometimes see that the USB driver is unable to allocate contiguous memory
for itself. For example I noticed that FreeBSD was unable to allocate
350kbytes of contiguous memory after that I had run "konqueror", the KDE web
browser and various other memory consuming applications for a while.
> No, sir. Operator precedence: assign first, and then compare, thus the
> comparison will always be true (else you'd be comparing to undefined
> values, which isn't any better). You might as well write:
>
> foo = malloc(0);
> /* make noise */
Ok, just for having it done:
if (foo == (
I went wandering through the C Working Group archives for the heck of
it, and apparently a lot of people were confused over this, thinking
either as you did or that "unique" meant it would a value unique to
the usage of malloc(0). It's been clarified recently (and will be in
the next revision of
On Fri, Jun 30, 2006 at 06:59:37AM +0200, Johannes Weiner wrote:
> Hi,
>
> On Thu, Jun 29, 2006 at 07:29:16PM +0200, Matthias Andree wrote:
> > No, sir. Operator precedence: assign first, and then compare, thus the
> > comparison will always be true (else you'd be comparing to undefined
> > values
On Friday 30 June 2006 04:49, Kamal R. Prasad wrote:
> Hello,
>
> I installed Freebsd 6.1 on an IBM(now lenovo) Thinkpad T40. The
> dmesg shows the following -which probably need some config changes.
>
> acpi0: on motherboard
> acpi_ec0: port 0x62, 0x66 on
> acpi0 acpi_bus_number: c
John-Mark Gurney wrote:
Gerald Heinig wrote this message on Fri, Jun 30, 2006 at 10:41 +0200:
On Fri, 2006-06-30 at 01:16 -0700, John-Mark Gurney wrote:
This has now been fixed by making the built in driver return a negative
value for the probe.. so your probe routine can return 0, a
Hi Guys,
On Fri, 2006-06-30 at 01:16 -0700, John-Mark Gurney wrote:
> [EMAIL PROTECTED] wrote this message on Fri, Jun 30, 2006 at 14:26 +0800:
> > I found the problem! It was caused by an existed ata driver in FreeBSD. I
> > have mentioned before that the existed ata driver can take over the
> >
Hello,
I installed Freebsd 6.1 on an IBM(now lenovo) Thinkpad T40. The dmesg shows
the following -which probably need some config changes.
acpi0: on motherboard
acpi_ec0: port 0x62, 0x66 on acpi0
acpi_bus_number: can't get _ADR
< same message repeated a number of times>
...
ugen0:
Gerald Heinig wrote this message on Fri, Jun 30, 2006 at 10:41 +0200:
> On Fri, 2006-06-30 at 01:16 -0700, John-Mark Gurney wrote:
> > This has now been fixed by making the built in driver return a negative
> > value for the probe.. so your probe routine can return 0, and it will
> > win the probe
[EMAIL PROTECTED] wrote this message on Fri, Jun 30, 2006 at 14:26 +0800:
> I found the problem! It was caused by an existed ata driver in FreeBSD. I
> have mentioned before that the existed ata driver can take over the
> management of our HBA card, leading to our driver can not probe our card! By
On Thu, 2006-Jun-29 15:09:23 -0700, Randall Hyde wrote:
>>How about feeding the C source through the preprocessor, stripping out
>>the #line directives, compiling it and posting the exact gcc error and
>>source context.
>
>Okay, I'll try that when I get home. But I was kind of under the
>impression
22 matches
Mail list logo
