similar to: [patch 0/5] i386-gdt-pda i386 gdt and pda updates

Hi Andi, This is a series of patches based on your latest queue (as of the other day, at least). It includes: - the most recent patch to compute the appropriate amount of percpu space to allocate, using a separate reservation for modules where needed. - make the percpu sections page-aligned, so that percpu variables can be page aligned if needed (which is used by gdt_page) -

Hi Andi, This is a series of patches based on your latest queue (as of the other day, at least). It includes: - the most recent patch to compute the appropriate amount of percpu space to allocate, using a separate reservation for modules where needed. - make the percpu sections page-aligned, so that percpu variables can be page aligned if needed (which is used by gdt_page) -

Hi Andi, This is a set of updates for the firstfloor patch queue. Quick rundown: revert-mm-x86_64-mm-account-for-module-percpu-space-separately-from-kernel-percpu.patch separate-module-percpu-space.patch Update the module percpu accounting patch fix-ff-allow-percpu-variables-to-be-page-aligned.patch Make sure the percpu memory allocation is page-aligned

Hi Andi, This is a set of updates for the firstfloor patch queue. Quick rundown: revert-mm-x86_64-mm-account-for-module-percpu-space-separately-from-kernel-percpu.patch separate-module-percpu-space.patch Update the module percpu accounting patch fix-ff-allow-percpu-variables-to-be-page-aligned.patch Make sure the percpu memory allocation is page-aligned

Hi Jeremy, all, Sorry this took so long, spent last week in Japan at OSDL conf then netconf. After several false starts, I ended up with a very simple implementation, which clashes significantly with your work since then 8(. I've pushed the patches anyway, but it's going to be significant work for me to re-merge them, so I wanted your feedback first. The first patch simply changes

Hi Jeremy, all, Sorry this took so long, spent last week in Japan at OSDL conf then netconf. After several false starts, I ended up with a very simple implementation, which clashes significantly with your work since then 8(. I've pushed the patches anyway, but it's going to be significant work for me to re-merge them, so I wanted your feedback first. The first patch simply changes

Hello! I''d like to gather some points about running a rails application on a PDA. As a condition I''d like to use Palm and Windows Mobile based PDA to target a huge user audience (this could be become difficult I know, only Windows Mobile for the start is although okay). I googled the last weeks and found out that there were only a few web browsers out there. E.g. Mozilla

Hi All, After hours of reading and trials, I got the following setup working... 1. Dell Axim X30 PocketPC with 802.11b wireless using DHCP with Open WEP -- successfully connected to --> 2. Laptop with DLink Airplus DWL-650+ PCMCIA wireless with ndiswrapper v1.1 driver with network bridge (wired + wireless) and running a DHCP server listening on interface br0 (eth0 + wlan0) Here is the

Can PDAs be used as softphones/clients on asterisk? what i wanted to do is to set up 2 PDAs as softphone(client) which allows them to communicate each other through asterisk server(desktop) devices i have: pda compaq model 3680 pda sharp sl5500 access point desktop(asterisk) can i apply my idea on the asterisk? any guides? thanks in advance :) --------------------------------- Do

Hi, Anyone has this working? Looks like there is a chicken-and-egg issue with pda setup: * xen_load_gdt() uses multicalls, thus depends on cpu-specific variables (per-cpu mc buffer) which in turn requires pda being setup already. * pda setup can't be done before xen_load_gdt() ... Next question while looking at xen_load_gdt(): why does it use multicalls in the first place?

Hi, Anyone has this working? Looks like there is a chicken-and-egg issue with pda setup: * xen_load_gdt() uses multicalls, thus depends on cpu-specific variables (per-cpu mc buffer) which in turn requires pda being setup already. * pda setup can't be done before xen_load_gdt() ... Next question while looking at xen_load_gdt(): why does it use multicalls in the first place?

I try to setup SJphone on my PDA, but it does not register with Asterisk. I have setup a sip account on asterisk, ... Can anybody give me a hint? bye Ronald

hello, i have a 5500 iPaq with familiar 0.8.2 on it and i don''t know how to install a traffic shaper tool on it. I installed iproute2 package i found on familiar site and for that i have the tc and ip commands, but when trying to add a qdisc, as a dummy example, i get the next answer: > tc qdisc add dev wlan0 root cbq bandwidth 100Mbit avpkt 100 RTNETLINK answers: Invalid argument

http://www.skype.net/download_pda.html http://australianit.news.com.au/articles/0,7204,9214802%5e16123%5e%5enbv %5e,00.html -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20040407/51a98542/attachment.htm

I need a new pda/smart phone that allows me to do some remote admin. Anyone know of anything that I can run a vpn and cli/ssh with? Thanks! jlc

2006/11/2, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca>: > > Today I tried speex echo cancellation on my VoIP application running > > on a windows mobile based PDA (OMAP1510 168MHz). The result is > > disappointing: it takes 150-250 ms to do echo cancellation (by calling > > speex_echo_capture() ) for a 20 ms frame! > > Are you by any chance using an insane

I did the test on another PDA which runs XScale 416Mhz CPU, the EAC arithmetic could be done in 1ms, but for the previous PDA (TI OMAP 168Mhz), it take more than 100ms! Though EAC could run in time on the new PDA, it did no help to cancel the echo, here is my test scenario: Init echo_state: echo_state=speex_echo_state_init(160,1120); int tmp=8000;

Seems to work OK for native and Xen. I had to play a bit with the paravirt-sched-clock patch to deal with the VMI changes. Zach, can you check that it still works? Thanks, J

Seems to work OK for native and Xen. I had to play a bit with the paravirt-sched-clock patch to deal with the VMI changes. Zach, can you check that it still works? Thanks, J

Hello all, Today I tried speex echo cancellation on my VoIP application running on a windows mobile based PDA (OMAP1510 168MHz). The result is disappointing: it takes 150-250 ms to do echo cancellation (by calling speex_echo_capture() ) for a 20 ms frame! I've defined the FIXED_POINT macro. Is there anyway to do some optimization? Nick