NetSurf on ARMv7 platforms
by John-Mark Bell
Afternoon,
So, NetSurf runs mostly ok on ARMv7 platforms with their backwards
incompatible unaligned LDR behaviour turned on. Tinct, however, appears
to perform some LDRs from unaligned addresses, resulting in crashes.
Here's a backtrace:
> Fatal signal received: Segmentation fault
>
> Stack backtrace:
>
> Running thread 0x59e53c
> ( 5a7ee0) pc: 462860 lr: 74f4c sp: 5a7ee4 __write_backtrace()
> ( 5a7f10) pc: 74d64 lr: 463298 sp: 5a7f14 ^ro_gui_signal()
> ( 5a7f38) pc: 463288 lr: 462f58 sp: 5a7f3c __unixlib_exec_sig()
> ( 5a7fa0) pc: 462a18 lr: 463870 sp: 5a7fa4 __unixlib_raise_signal()
> ( 5a7fb0) pc: 463774 lr: 5a6c48 sp: 5a6c04 __h_cback()
>
> Register dump at 005a7fb4:
>
> a1: 12f a2: 2d a3: 1f4 a4: 0
> v1: 0 v2: 0 v3: 202513b4 v4: 1
> v5: 3d5 v6: 0 sl: 41b78d39 fp: 67197124
> ip: 20248394 sp: 5a6c04 lr: 5a6c48 pc: 2024609c
> cpsr: 80000113
>
> 20246088 : .p.â : e21a7003 : ANDS R7,R10,#3
> 2024608c : .... : 0a000008 : BEQ &202460B4
> 20246090 : .àgâ : e267e003 : RSB R14,R7,#3
> 20246094 : ..^á : e15e0000 : CMP R14,R0
> 20246098 : .à Á : c1a0e000 : MOVGT R14,R0
> 2024609c : .??å : e59a9000 : LDR R9,[R10,#0]
> 202460a0 : ..@Ð : d040000e : SUBLE R0,R0,R14
> 202460a4 : ..?Ò : d2800003 : ADDLE R0,R0,#3
> 202460a8 : ..?À : c0800007 : ADDGT R0,R0,R7
>
> Invalid pc address bebeec
For reference, Tinct is loaded at 202416B4.
J.
13 years, 3 months
Netsurf for the nintendo ds
by Olivier BINDA
Hello.
In order to improve a flashcard program for the Nintendo DS (an Anki client), I'm looking for a way to display
very simple Html files with pictures and css formatting inside a C/C++ project. And so, I was wondering :
1) Would it be possible to build and use netsurf for the nintendo dsi, considering that it has the following specs
:
16 MB of RAM of mobile RAM,
Two 3-inch TFT LCDs, 18-bit depth (262,144 colors), resolution of 256 x 192 pixels,
256 MB of internal flash memory with an SD card (up to 2 GB) and SDHC card (up to 32 GB) expansion slot
two ARM architecture CPUs; ARM9 and ARM7.[40] The main CPU is clocked at 133 MHz
2) If it is possible, I might want to build netsurf with the framebuffer and SDL targets, but will I be able to
use/embed netsurf inside my program ?
What will be the limitations, considering the two screens and input ?
3) I have somehow successfully built some libraries for the Nintendo ds (using a custom makefile) :
SDL, Freetype, expat, zlig, giflib, pnglib, cyassl
So I'm not a complete noob, but I'm not very experienced in the c/c++/makefile business either.
Will it be hard/a lot of work to port/use Netsurf for the nintendo ds ?
I gave it a go and...if I'm not mistaken, I have to set up pkg-config, perl and to build all the specific netsurf
libraries (libcss, libnsbmp, hubub,libwapcaplet,libnsfb, etc)
before I can give a try at building netsurf, right ?
(I'm a bit at a loss, what to do with the makefile files that come with the netsurf/library source code...)
Thanks in advance,
Olivier Binda
13 years, 9 months
Call for participation to the "Alt-OS" devroom at FOSDEM
by François Revol
During the previous edition of the Free and Open Source Software
Developer's European Meeting (FOSDEM) <http://fosdem.org/>, several
alternative FOSS Operating System projects
(Haiku <http://haiku-os.org/>, ReactOS <http://www.reactos.org/>)
shared booths, but there were discussions about going beyond presenting
each projects on its own, and instead seek cooperation. Recently, at
the Google Summer of Code mentor summit, other OS projects gathered and
formed the Rosetta OS group <http://code.google.com/p/rosetta-os/> to
work on driver sharing.
This year, the FOSDEM (in Brussels, 6-7th February 2010) will host the
"Alt-OS" devroom on sunday from 9:00 to 17:00, organized by members of
the Rosetta OS project.
This devroom is meant as a place for Free and OpenSource Alternative
Operating System projects to share ideas and work on topics like:
* distinguishing design and features,
* device drivers and how to share them,
* sharing code for internal components,
* internal usage of other FOSS projects to build upon,
* application portability,
* interoperability,
* file formats,
* extended attributes...
We are interested to hear about your OS projects, how they are
designed, and what they could eventually share for other projects'
benefit.
In addition to all FOSS OS projects, any application project that is
seeking new target platforms is invited. Featured projects will include
participants from the Rosetta OS project which charter <http://code.google.com/p/rosetta-os/wiki/RosettaOSCharter>
matches our devroom goal.
As time allows, we are also interested in transversal subjects in
cooperation with other devrooms. As an example, possible topics could
include:
* unusual package management with the Crossdistro room,
* standardization of GUI elements and behavior with the Crossdesktop
devroom,
* scalability with the Embedded devroom,
* ways in which BSD drivers were reused in your project,
* concerns about porting Java,
* Gallium3D port progress reports...
The format of the talks can vary, from 45min large speech to 15 min
general project presentation, or hand-on hacking session.
= Proposals =
Proposals should be sent to François Revol by mail: revol(a)free.fr
Your proposal should include:
* duration (in 15 minute blocks -- please stick with that granularity,
as it will make the schedule somewhat easier to follow for visitors),
* activity title (please try to be descriptive, there are ~250 talks
at FOSDEM during the week-end ;)),
* a short abstract (1-2 paragraphs),
* a longer description if appropriate,
* optionally a list of links to the project website or similar
* for each speaker:
* the speaker's real name,
* a short overview of her bio in a couple of lines,
* optionally also a longer bio,
* optionally a picture (please send it to us as 128x128 PNG),
* optionally links to her website, blog, ...
Plain-text format is preferred by the FOSDEM team, it makes their life
easier, something like:
------------------
John Doe
john.doe(a)example.org
John is currently working as a freelancer and spends most of his free
time contributing to various opensource projects, most prominently on
libjohndoe.
John currently lives in England with his wife, 2 kids and a bunch of
kitten. He loves spending his time walking around in the woods, and
of course kitten. He has a masters degree in kitten science, which
helps him a lot with coding.
blog: http://johndoe.example.org/blog/
attached: john_doe.png
------------------
= Deadline =
The deadline for submissions is 2009-12-25, please try to stick to it.
Acceptance notification on 2009-12-31.
= Organization =
The room provided by the FOSDEM team has:
* room number AW1.105 with 48 seats,
* a video projector with VGA cable,
* wireless internet.
We will try to provide a wifi router with ethernet ports for
demonstrations since we know many projects do not have functional wifi
drivers yet.
We will also try to provide a laptop to load your slides on if you
can't use your own machine.
It is advised to see with your project supporting associations for
possible reimbursement of travel and hosting cost, since the FOSDEM
team cannot help there. Attendance is free however.
Also remember to check other devroom calls as well as the call for
lightning talks <http://fosdem.org/2010/call_for_lightningtalks>, for
subjects that might not fit our topics of interest.
= Projected schedule =
9:00 Welcome (15min)
9:15 "Rosetta OS" project
morning project presentations, design...
afternoon more projects, workshops...
16:45 Closing (15min)
13 years, 9 months
framebuffer draw problems with links that want open a new window
by Bernd Roesch
Hi,
when click on links that want open a new browser window(for example banner
or large image show), netsurf show the
page in the main window, because framebuffer have only 1 window.
thats ok when only 1 window can use, but when scroll on the page, the
content of the old page is draw and move more and more in on more scroll.
Is there a way possible that netsurf ignore this new window open complete,
so all is as click on a normal link and with the back button can see the
previous page ?
Bye
13 years, 9 months
