tag:blogger.com,1999:blog-3519606278200777308.comments2023-10-20T23:01:01.979+08:00olvolvhttp://www.blogger.com/profile/14109154724494271204noreply@blogger.comBlogger33125tag:blogger.com,1999:blog-3519606278200777308.post-1164977898691788582010-09-30T19:34:03.765+08:002010-09-30T19:34:03.765+08:00I have done the same benchmark, hash+loop is faste...I have done the same benchmark, hash+loop is faster e.g. [4] bits hash with 8 loop count with optimization and do it alot of time. Possible because of the cpu instruction cache.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-85084291587573323162010-02-28T19:41:20.143+08:002010-02-28T19:41:20.143+08:00是card0不是card"o"
我是去年osdc上跟你討論過linux drm...是card0不是card"o"<br /><br />我是去年osdc上跟你討論過linux drm的DavidDavid Wanghttps://www.blogger.com/profile/05711631324564216507noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-80577044552481781852009-12-30T11:54:26.649+08:002009-12-30T11:54:26.649+08:00Wow! I like cube. :)Wow! I like cube. :)charlesnoreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-30894732266072292822009-11-30T13:49:49.821+08:002009-11-30T13:49:49.821+08:00所以我說在做"benchmark" 的情況下嘛,真實的狀況不太可能一直做bitc...所以我說在做"benchmark" 的情況下嘛,真實的狀況不太可能一直做bitcount(我自以為),table 那麼大一張,cache 又不是只有他在用,我只看過32bit 資料http://gurmeetsingh.wordpress.com/2008/08/05/fast-bit-counting-routines/Chih-Min Chaohttps://www.blogger.com/profile/00222401438234767130noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-74890717656281454542009-11-30T12:47:07.865+08:002009-11-30T12:47:07.865+08:00查表法比較直覺,但不必然比較快。32-bits 的數用 8-bits 的表查 4 次應該是做 3 次...查表法比較直覺,但不必然比較快。32-bits 的數用 8-bits 的表查 4 次應該是做 3 次加法、3 次 shift 跟 3 次 mask;如果是 64-bits 的數則會需要各做 7 次。bitcount 則是固定各做 4 次。<br /><br />利用討論串提到的 benchmark 測,32-bits 的情況下查表法比 bitcount 快大概 30%;但 64-bits 的情況下查表法會慢大概 40%。<br /><br />不過如果改用 16-bits 的表查,那查表法又會贏回來。但這是不考慮 cache miss 的情形。olvhttps://www.blogger.com/profile/14109154724494271204noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-49675370916618186572009-11-30T11:05:26.961+08:002009-11-30T11:05:26.961+08:00如果是在做benchmark 的情況下,查表法是最快的如果是在做benchmark 的情況下,查表法是最快的Chih-Min Chaohttps://www.blogger.com/profile/00222401438234767130noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-17012883895803385932009-11-30T09:29:45.189+08:002009-11-30T09:29:45.189+08:00Divide and conquer!!!Divide and conquer!!!AZ Huanghttps://www.blogger.com/profile/05164412344318795173noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-63089489052973339792009-11-30T02:02:01.175+08:002009-11-30T02:02:01.175+08:00this is you, right?!
http://www.phoronix.com/scan....this is you, right?!<br />http://www.phoronix.com/scan.php?page=news_item&px=NzY4OAerinhttps://www.blogger.com/profile/17766743879857803642noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-5165643178890416512009-11-28T11:08:54.188+08:002009-11-28T11:08:54.188+08:00看到標題,我還以為能夠在Android上使用Google Wave,看來我錯了…^^看到標題,我還以為能夠在Android上使用Google Wave,看來我錯了…^^Nickyhttps://www.blogger.com/profile/03976895842570948954noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-37478103987216578442009-09-24T09:52:55.442+08:002009-09-24T09:52:55.442+08:00您好, 不好意思, 您的投影片與Demo Code連結失效, 還有機會取得嗎? 謝謝.您好, 不好意思, 您的投影片與Demo Code連結失效, 還有機會取得嗎? 謝謝.YFhttps://www.blogger.com/profile/01992527278203374734noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-13408868105862662812009-08-24T10:40:59.205+08:002009-08-24T10:40:59.205+08:00我是讀 kernel 的 source code。我是讀 kernel 的 source code。olvhttps://www.blogger.com/profile/14109154724494271204noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-23017099103109846902009-08-21T23:04:52.092+08:002009-08-21T23:04:52.092+08:00olv 大大讀的到底是什麼書才會作這個筆記呀?olv 大大讀的到底是什麼書才會作這個筆記呀?Anonymoushttps://www.blogger.com/profile/09022680447812172669noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-84861543475460246832009-06-11T23:45:01.224+08:002009-06-11T23:45:01.224+08:00"不晃","會被撞","到地上""不晃","會被撞","到地上"Jeremyhttps://www.blogger.com/profile/03949422596172627364noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-72334071863936226992009-06-04T17:46:13.926+08:002009-06-04T17:46:13.926+08:00我沒試過,不過可以參考
frameworks/base/core/jni/android_view...我沒試過,不過可以參考<br /><br />frameworks/base/core/jni/android_view_Surface.cpp 的 setSurface 看看。olvhttps://www.blogger.com/profile/14109154724494271204noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-69726586885159568732009-05-27T17:45:10.374+08:002009-05-27T17:45:10.374+08:00今天看了 Wayland 論壇上的 Lessons learned from QWS 發現這邊的討論...今天看了 Wayland 論壇上的 <A HREF="http://groups.google.com/group/wayland-display-server/msg/92dbc8225fba2d53?" REL="nofollow">Lessons learned from QWS</A> 發現這邊的討論似乎是說,即使沒有硬體加速的一般顯示卡 Wayland 也能在上面執行:<br /><br />Question by Tom Cooksey:<br /><br />One last thing - have you thought about non-GL hardware? I think it would be pretty easy to implement all this in software or with simple blit-only type hardware. These nasty things aren't ever going away - there'll always be a bottom end market segment with no HW acceleration. The question is - should they be in scope? Personally I'd like to see Wayland be _the_ graphics API on Linux, in which case it will have to support these kind of devices.<br /><br />Answer by Kristian Høgsberg:<br /><br />Sure, that's how wayland started out :) It's all in the clients and compositor. The only requirement in the core is that you have a memory manager/shared memory mechanism in place that lets you identify buffers by an integer. How you go from buffer contents to handle and vice versa is up to the clients and the compositor. Except for the egl gears I added to the window.c client recently, all clients were just using cairo sw rendering and pushing that into a gem buffer. And the initial compositor would just mmap /dev/fb and memcpy the pixels in there.<br /><br />如果 Kristian 所言屬實,那麼問題就回歸到上次您提到 GEM 的缺點上 (或是 driver 支不支援的問題),而與顯示卡硬體的新、舊、優、劣都沒有關係 ... 所以我想最後問題可能還是落在 driver 的支援性或是廠商是否公佈 data sheet 的問題上,排除這些問題 Wayland 應是大有可為。Anonymoushttps://www.blogger.com/profile/14075835666526491546noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-36283470312111582922009-05-27T15:57:35.141+08:002009-05-27T15:57:35.141+08:00您好,我們想在Java App create一個Surface,然後像你一樣用native libr...您好,我們想在Java App create一個Surface,然後像你一樣用native library在這個Surface上繪圖。<br />我們的想法是,將App創建的Surface透過JNI丟給native library。<br />請問您知道怎麼在Java App中得到可以往下丟的Surface記憶體位置嗎?<br />謝謝!Romulushttps://www.blogger.com/profile/16950046628704622532noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-11370928205672910492009-05-16T19:57:00.000+08:002009-05-16T19:57:00.000+08:00請參考新發表的 Android Window System。請參考新發表的 <A HREF="http://olvaffe.blogspot.com/2009/05/android-window-system.html" REL="nofollow">Android Window System</A>。olvhttps://www.blogger.com/profile/14109154724494271204noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-19271057400389199852009-05-14T17:58:00.000+08:002009-05-14T17:58:00.000+08:00这个非常有趣, 能详细说一下么, 谢谢!这个非常有趣, 能详细说一下么, 谢谢!flying without wingshttps://www.blogger.com/profile/07954203099108982889noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-38066798403639160152009-05-07T00:02:00.000+08:002009-05-07T00:02:00.000+08:00在 Jserv MicroXwin 文章裡提到:「...MicroXwin 的思維乃是著眼於拜自由軟...在 Jserv <A HREF="http://blog.linux.org.tw/~jserv/archives/002075.html" REL="nofollow">MicroXwin 文章</A>裡提到:「...MicroXwin 的思維乃是著眼於拜自由軟體蓬勃發展所賜,豐富的 X 應用程式有如過江之鯽,但,在有限硬體能力的嵌入式環境中,是否有機會獲得良好的呈現與使用者互動能力呢?...」。<br /><br />承接上下文,上面這句話言下之意應是說,在有限硬體能力之下 MicroXwin 確實可以改善圖形的效能,這裡所謂的硬體應該就是指硬體加速的機制,換句話說, 在沒有硬體加速機制的情況下 MicroXwin 仍然可以提升圖形的效能...不過這不禁讓我懷疑,當在沒有硬體加速機制的情況下 Wayland 是否也同 MicroXwin 能夠改善圖形的效能?如果繼續往下讀,問題似乎變得更明朗:<br /><br />Jserv:「...在沒有特殊硬體加速機制 (如 DRI 與 GLX/OpenGL) 的前提,以下因素導致原本 X Window System 效能低落並佔用系統資源...」。<br /><br />雖然對 DRI/DRI2 以及 Wayland 的了解非常有限,但就我個人的認知如果沒錯的話,Wayland 是需要依賴 DRI/DRI2 來運作的,此外 DRI/DRI2 同時也是 Wayland 之所以能夠改善圖形效能的關鍵因素,而 Jserv 上面那句話言下之意應是說 DRI/DRI2 無法在沒有硬體加速的機制下運作,這間說明了:Wayland 要能夠正常運作,必須要有硬體加速 (即 2D??/3D 加速卡) 的配合。<br /><br />如果上面的推論沒錯的話,那麼 Wayland 能夠應用的範圍可能還是有其限制。因為不只是嵌入式的系統,甚至是連一般個人電腦也都不見得會安裝 3D 加速卡,這聽起來實在是讓人感到有點遺憾。如果 Linux 的 GUI 要能夠媲美 Windows 的圖形效能,除非能夠確定加速卡將會在個人電腦及嵌入式系統迅速地普及化,否則這方面可能還有改進的空間。Anonymoushttps://www.blogger.com/profile/14075835666526491546noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-62031554423387394412009-05-04T19:35:00.000+08:002009-05-04T19:35:00.000+08:00我會努力盡早生出來 :P我會努力盡早生出來 :Polvhttps://www.blogger.com/profile/14109154724494271204noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-16545774774082022722009-05-04T17:41:00.000+08:002009-05-04T17:41:00.000+08:00问题已经解决,是qemu不支持kernel的vga=xxx的属性,我是想用qemu直接load内核。...问题已经解决,是qemu不支持kernel的vga=xxx的属性,我是想用qemu直接load内核。Coolperhttps://www.blogger.com/profile/07243987486790190634noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-63260295564161424852009-04-30T17:47:00.000+08:002009-04-30T17:47:00.000+08:00谢谢回答。
我目前遇到的问题是能够看到android界面,但是颜色不对,好像是16色的,另外,鼠标点...谢谢回答。<br />我目前遇到的问题是能够看到android界面,但是颜色不对,好像是16色的,另外,鼠标点击没有任何响应,期待您的答复。Coolperhttps://www.blogger.com/profile/07243987486790190634noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-41842325342105161072009-04-30T14:16:00.000+08:002009-04-30T14:16:00.000+08:00你好, 可否請你詳細說明一下, 如何在 Android 下跑 cairo 的時鐘 。
謝謝 !你好, 可否請你詳細說明一下, 如何在 Android 下跑 cairo 的時鐘 。<br />謝謝 !Michaelhttps://www.blogger.com/profile/13078338669215705799noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-13559193381399758432009-04-30T09:37:00.000+08:002009-04-30T09:37:00.000+08:00你可以利用 adb logcat 看能不能發現 UI 起不來的原因。通常我會
$ qemu -hd...你可以利用 adb logcat 看能不能發現 UI 起不來的原因。通常我會<br /><br />$ qemu -hda disk.img -redir tcp:5555::5555<br /><br />啟動 qemu。然後<br /><br />$ adb kill-server<br />$ adb logcat 或 adb shell<br /><br />來看 log。有問題歡迎問我,更詳細的步驟可能要請你 google 找找看。<br /><br />這篇文章的 patch 在這個 <A HREF="http://android.git.kernel.org/?p=platform/frameworks/base.git;a=commit;h=37f8ca1e33a7e92f134344b26780e9a8e0329287" REL="nofollow">commit</A> 之後已經不需要了。olvhttps://www.blogger.com/profile/14109154724494271204noreply@blogger.comtag:blogger.com,1999:blog-3519606278200777308.post-18071150115972554702009-04-30T09:21:00.000+08:002009-04-30T09:21:00.000+08:00你好,请问你能不能把在qemu上运行X86 android的比较详细的步骤张贴出来?我编译的eee_...你好,请问你能不能把在qemu上运行X86 android的比较详细的步骤张贴出来?我编译的eee_701 x86 android总是看不到图形界面。谢谢!Coolperhttps://www.blogger.com/profile/07243987486790190634noreply@blogger.com