Development

The ipro1000 driver wrapper driver.c only recgonizes a small subset of the PCI IDs that are listed as supported by the underlying FreeBSD driver (the list in e1000_hw.h ) and also doesn't provide an "escape hatch" based on a setting in the driver config file.

It'd be good if the ipro1000 driver could provide an escape hatch mechanism via its config file, so testing the driver with a new card didn't require rebuilding it. It'd also be great if it listed support for all of the devices in e1000_hw.h of course.

(My ulterior motive here is to get networking up & running on my Asus Z97-PRO, which has an Intel I218-V, which should be supported by this driver.)

On Mon, Nov 17, 2014 at 12:44 PM, François Revol revol@xxxxxxx wrote: On 17/11/2014 00:16, François Revol wrote: Hi, I was saving my blog post when suddently the website went out of business... First it failed to save, then it said I never created any blog post. ...

260 MB

260 MB

262 MB

262 MB

* SD cards are "blessed" with a boot0 spl and boot1 u-boot at fixed locations. * Allwinner's u-boot is lacking a lot. * Upstream u-boot should be better at some point. WIP: http://lists.denx.de/pipermail/u-boot/2015-January/201537.html * SD cards are "blessed" with a boot0 spl and boot1 u-boot at fixed locations. * Allwinner's u-boot is lacking a lot. * Upstream u-boot should be better at some point. WIP: http://lists.denx.de/pipermail/u-boot/2015-January/201537.html

This reverts the other half of b959d46dbd2f9087ae860dbced40440c28596a6e. This reverts the other half of b959d46dbd2f9087ae860dbced40440c28596a6e.

The stack base and end addresses are stored in TLS slots that are prepared when enabling stack traces and filled in lazily on use for each thread. This avoids the need of calling get_thread_info to get these values. Also simplifies the code somewhat due to proper frame skipping support. The stack base and end addresses are stored in TLS slots that are prepared when enabling stack traces and filled in lazily on use for each thread. This avoids the need of calling get_thread_info to get these values. Also simplifies the code somewhat due to proper frame skipping support.

It can be used to get a stack trace of the current thread. Note that this works by walking frame pointers and will not produce anything useful if an application is compiled with the frame pointers omitted. The stack base and end addresses have to be provided as arguments and are used to check that the frame pointers fall within that range. These values are thread specific and can be retrieved with get_thread_info(). No other sanity checks (like checking for loops in the linked list) are done. This is a simplified rewrite of the stack trace code from the kernel debugger. As this code is common to x86 and x86_64 but is not generic across architectures I introduced x86_common as a directory to put such sources. It can be used to get a stack trace of the current thread. Note that this works by walking frame pointers and will not produce anything useful if an application is compiled with the frame pointers omitted. The stack base and end addresses have to be provided as arguments and are used to check that the frame pointers fall within that range. These values are thread specific and can be retrieved with get_thread_info(). No other sanity checks (like checking for loops in the linked list) are done. This is a simplified rewrite of the stack trace code from the kernel debugger. As this code is common to x86 and x86_64 but is not generic across architectures I introduced x86_common as a directory to put such sources.

On 17/11/2014 00:16, François Revol wrote: Hi, I was saving my blog post when suddently the website went out of business... First it failed to save, then it said I never created any blog post. And then I noticed the front page was gone as well: Welcome to your new Drupal website! ...

Hi, I was saving my blog post when suddently the website went out of business... First it failed to save, then it said I never created any blog post. And then I noticed the front page was gone as well: Welcome to your new Drupal website! ...

Haiku is among 12 orgs to be selected for Google Code-In 2014. We are now populating the task list and getting mentors signed into melange. If you are over 18 and would like to mentor for Haiku this year, please contact me offlist. Contest starts on Dec 1st. -scott ...

$375-$500 day Online BB starts October 10 to 30 Incentive: $375-$500 Details: 20 Day Online Bulletin Board Dates: October 10 to October 30 We are thrilled that you would like to share your views and participate in this research project. Please click on the link below to answer a few screening questions for this study. If you appear to qualify based on your answers, a Focus Forward representative will contact you with additional details. ...

fixed

This was most prominently visible in applications that show a lot of icons like Tracker and Deskbar. This was most prominently visible in applications that show a lot of icons like Tracker and Deskbar.

Calling Quit() on the window deletes it, so using the fTextControl member to get the result does not work. Calling Quit() on the window deletes it, so using the fTextControl member to get the result does not work.