Hi,
We tried Codesourcery's toolchain (lite) 4.2.0/4.2.3, the
compiler/linker option -Wl,-elf2flt='-z' is not working in
our environment.
Kind regards
Teun Grinwis
Markus Franke wrote:
Hi Jun,
Jun Sun schrieb:
This might be a dumb question, but have we considered moving to gcc4.x
for
Mihir Sevak schrieb:
how about using netlink - socket approach ?
Hmmm.sounds quite interestingwill go through some documentation.
So you think with netlink it is possible to communicate data between
user and kernel space via a normal socket api interface?
Thanks for the hint and
Hi Gavin,
Gavin Lambert schrieb:
While it's generally considered to be bad style, in fact *because* of the
lack of MMU support you can usually just pass a raw pointer from kernel to
user space and the user code can just read (or even write) it directly.
yeahthought about this as well but
AFAIK, you can allocate a memory area with the driver during the
initialization and when the user app calls the diver e.g. in a read
request, have the driver calculate the user space address and pass as
data it to the user program. Maybe the scull example in Linux device
drivers can offer
Hi Markus,
Markus Franke wrote:
Greg Ungerer schrieb:
The kernel can do basic profiling already. Supply a profile=4 boot
option to it. And read out the profile information use the readprofile
app.
yes I know about this option. I tried with profile=2 but readprofile
gave me only very little
On Sun, Jul 13, 2008 at 10:02:08PM +1000, Greg Ungerer wrote:
Hi Jun Sun,
Jun Sun wrote:
This might be a dumb question, but have we considered moving to gcc4.x
for uclinux? Any pro's and con's? What would be the effort to do so?
I have been using a gcc-4.2.4 based toolchain for ColdFire
Hi Jun,
Jun Sun wrote:
On Sun, Jul 13, 2008 at 10:02:08PM +1000, Greg Ungerer wrote:
Jun Sun wrote:
This might be a dumb question, but have we considered moving to gcc4.x
for uclinux? Any pro's and con's? What would be the effort to do so?
I have been using a gcc-4.2.4 based toolchain for
