All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>
To: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Questions about ti-syslink-module
Date: Wed, 14 Dec 2011 12:43:08 +0100	[thread overview]
Message-ID: <4EE88BCC.8070502@ts.fujitsu.com> (raw)

Hi there,

still playing around with my dm814x-evm board and at least now I
successfully builded a systemd-gnome-image that runs if you add syslink
from the TI EZSDK 5.02 and some firmware files. I tried to build those
things, so I include ti-syslink-module in my build, and I also made a
recipe to copy the firmware binaries to the /usr/share/ti/... direcotries.

The problem is, that this image crashes as soon as I load the vpss
firmware.

At the moment I wonder if syslink is the cause of the problem. Looking
at the recipe in meta-ti I see that it builds a version 2_00_00_78, but
the EZSDK 5.02 uses 2_00_00_80.

The other thing that puzzles me is that my kernel config has
CONFIG_Sys_Link=y
CONFIG_SYSLINK_MULTIPROC=y
CONFIG_SYSLINK_NOTIFY=y

What part of syslink is that which is already in the kernel sources?

At the moment it looks all confusing and I guess that the crashes come
from version mixing, but I'm not sure.

Best regards
Rainer
-- 
Dipl.-Inf. (FH) Rainer Koenig
Project Manager Linux Clients
Dept. PDG WPS R&D SW OSE

Fujitsu Technology Solutions
Bürgermeister-Ullrich-Str. 100
86199 Augsburg
Germany

Telephone: +49-821-804-3321
Telefax:   +49-821-804-2131
Mail:      mailto:Rainer.Koenig@ts.fujitsu.com

Internet         ts.fujtsu.com
Company Details  ts.fujitsu.com/imprint.html


             reply	other threads:[~2011-12-14 11:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14 11:43 Rainer Koenig [this message]
2011-12-14 12:29 ` Questions about ti-syslink-module Monk, Roger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EE88BCC.8070502@ts.fujitsu.com \
    --to=rainer.koenig@ts.fujitsu.com \
    --cc=meta-ti@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.