Rockbox mail archive

• Next message: alankorr: "(no subject)"
• Next in thread: Bjorn.Stenberg_at_contactor.se: "Re: some basic dev questions"
• Maybe reply: Bjorn.Stenberg_at_contactor.se: "Re: some basic dev questions"
• Maybe reply: Stuart Martin: "RE: some basic dev questions"
• Maybe reply: Bjorn.Stenberg_at_contactor.se: "Re: some basic dev questions"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Hi guys

I have a background in programming, but little in the way of electronics,
and as such, I have a few questions about the project. Forgive me if my
high-level mindset misses the mark too often.

 o Are the character font sizes fixed on the LCDs or are they variable?

 o What is the quality of the gcc generated code? With such a small
   footprint available, would assembler be a better bet? I've no idea,
   just thinking aloud here.

 o Are there any (tiny or otherwise) OSs already written
   that we could obtain/use/modify? If there are, would such an approach
   be sensible? After all, an OS typically provides raw services
   for client applications, whereas we would have just a single
   application, no? Is this right, or can anyone envisage a need
   for scheduling/multiprocessing? Does this require CPU support?

 o Is there any argument for the immediate development of high-level
   components of prospective applications before the low-level
   interfaces are completed? I know that this is the hacker mentality
   coming to the fore :) but application developers could make
   progress on core features (music control, playlist manipulation, etc)
   independently of the work being carried out on the metal itself.

 o Is the CPU capable of decoding other music formats in real-time,
   or is dedicated chip support necessary for this?

 o Which low-level components need developing before we can begin to
   replace the archos-provided code? I know the MP3 en/decoding is done
   on chip - do any more of these come for 'free'?
    o USB driver code?
    o IDE controller code?
    o LCD driver code (exciting to see the preliminary work done here)
    o MP3 decoding drivers?

an aside:

 o Is it possible to write code to dump the *rom* firmware to a file? If
   so, would this be directly usable as (or convertable into) a mod file
   for others? I'm thinking about newer models with firmware on rom
   (rather than shipped as updates).

regards,
wavey

---------------------------------------------------------------------------
LATEST NEWS FROM VALTECH
CRM - Delivering on expectations
John Plumpton, Senior Business Consultant at Valtech, has written an article
for CommsDealer in which he outlines how a properly structured CRM solution
can provide much-needed competitive advantage. To read the article, please
visit the pressroom at http://www.valtech.co.uk

DISCLAIMER: This e-mail contains Proprietary information some or all of
which may be legally privileged. It is for the intended recipient only.
If an addressing or transmission error has misdirected this e-mail,
please notify the author by replying to this e-mail.
If you are not the intended recipient you must not disclose, distribute,
copy, print or rely on this e-mail.
All information contained within this e-mail is subject to the Terms &
Conditions of Valtech Ltd. which are available upon request.

• Next message: alankorr: "(no subject)"
• Next in thread: Bjorn.Stenberg_at_contactor.se: "Re: some basic dev questions"
• Maybe reply: Bjorn.Stenberg_at_contactor.se: "Re: some basic dev questions"
• Maybe reply: Stuart Martin: "RE: some basic dev questions"
• Maybe reply: Bjorn.Stenberg_at_contactor.se: "Re: some basic dev questions"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]