TPEGFX/2014-08-28: Difference between revisions
< TPEGFX
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
** Some note here: | ** Some note here: | ||
** - Flame(QCT) devices can access any buffer post to fb_dev, but Dolphin(SPRD) not, Dolphin require different buffers for each frame | ** - Flame(QCT) devices can access any buffer post to fb_dev, but Dolphin(SPRD) not, Dolphin require different buffers for each frame | ||
** => So BufferQueue::cancel_buffer trick not work for Dolphin. | ** => So BufferQueue::cancel_buffer trick do not work for Dolphin. | ||
** - Adreno GL driver do not call setBufferCount on init, and its BufferQueue does not complain about it, but Dolphin need setBufferCount, otherwise BufferQueue can not contains more than 1 buffer. | ** - Adreno GL driver do not call setBufferCount on init, and its BufferQueue does not complain about it, but Dolphin need setBufferCount, otherwise BufferQueue can not contains more than 1 buffer. | ||
** - Both GL driver calls to connect while GL init before dequeueBuffer(back buffer), and BufferQueue::connect implies ConsumerBase::onBuffersReleased if the BufferQueue hasn't connected. | ** - Both GL driver calls to connect while GL init before dequeueBuffer(back buffer), and BufferQueue::connect implies ConsumerBase::onBuffersReleased if the BufferQueue hasn't connected. | ||
Revision as of 02:20, 28 August 2014
Weekly Report
Boris Chiou
Chiajung Hung
- bug 1055457 - Dynamic switch BootAnimation backend
- WIP
- Some note here:
- - Flame(QCT) devices can access any buffer post to fb_dev, but Dolphin(SPRD) not, Dolphin require different buffers for each frame
- => So BufferQueue::cancel_buffer trick do not work for Dolphin.
- - Adreno GL driver do not call setBufferCount on init, and its BufferQueue does not complain about it, but Dolphin need setBufferCount, otherwise BufferQueue can not contains more than 1 buffer.
- - Both GL driver calls to connect while GL init before dequeueBuffer(back buffer), and BufferQueue::connect implies ConsumerBase::onBuffersReleased if the BufferQueue hasn't connected.
- bug 1054929 - Black screen happens when writing in Canvas - GraphicBufferMapper failure: lock(...) failed -22 (Invalid argument)
- Debug
Jerry Shih
Morris Tseng
Tingyu Lin
- bug 1029943 - [Text selection] Enable selection carets on B2G and fix the existing test case failures
- debug
- bug 1057256 - [Text selection] Fix Mnw failed on b2g emulator after enabling selection carets
- r+
Solomon Chiou
Peter Chang
Rule of Thumb
Status code:
- OOAD: In analysis or design phase.
- WIP: working on WIP patch.
- feedback(f): feedback a patch
- feedback?(f?): WIP is ready for feedback grant.
- feedback+(f+): Get positive feedback.
- feedback-(f-): Get negative feedback.
- review(r): review a patch.
- review?(r?): patch is under review
- review+(r+): get review+ and ready to check-in
- review-(r-): get negative review feedback. Fix problems and switch back to r? again.
- land: patch check in.
- debug: Figure out the root cause of a bug/ try to repro that bug, etc...
- file: file a bug
- PTO: take personal leave
- interview(I)
- study: Spend time on domain knowledge study, such as multimedia transport technology, compress format, real-time rendering.
- presentation
- Write a personal blog, which is relative to work, such as articles on MozTech, or what you experience in a work week.
- WIKI/ MDN article writing.
- If you write a technical blog or anything relative to work, it's welcome to share it on weekly report.
- Do a presentation of technical topics
Status code combination rule
Combine status code with "|". For example
** OOAD|WIP
Which means you work on both OOAD and WIP in the last week.
land status code
If your patch is target for specific branch, instead of central, postfix branch version. For exp
** land(1.4)