Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] simicsfs 1.18 does not build with kernel 4.12.2
Date: Thu, 24 Aug 2017 23:02:11 +0200	[thread overview]
Message-ID: <20170824230211.4c0ea814@windsurf> (raw)
In-Reply-To: <CANQCQpY+iyQ5XtTA5tCh9V9awNa4fhGzJ+bmBdY1YWODuxjppQ@mail.gmail.com>

Hello,

On Thu, 24 Aug 2017 12:50:20 -0500, Matthew Weber wrote:

> > Unfortunately, simicsfs is no longer available at
> > http://download.simics.net/pub/simicsfs-1.18.tar.gz, where Buildroot
> > currently downloads it. The build only succeeds because we have a
> > backup of this tarball at http://sources.buildroot.net.
> 
> The project I originally did the 1.18 integration on completed ~2yrs
> back and my access to WindRiver Simics material is now gone.  It's too
> bad they didn't keep this driver public, however you may check with
> your WindRiver Simics contacts to see if they just moved the site and
> you could propose an update to this Buildroot package fixing support.

To be honest, since the source code is no longer available online, I'm
not sure it's really worth keeping this package in Buildroot. Let's see
if Bin gets some feedback from Windriver about putting the tarball back
online, publicly available. If there is no feedback, we'll drop the
package I believe.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-08-24 21:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 12:47 [Buildroot] simicsfs 1.18 does not build with kernel 4.12.2 Bin Meng
2017-08-24 17:33 ` Thomas Petazzoni
2017-08-24 17:50   ` Matthew Weber
2017-08-24 21:02     ` Thomas Petazzoni [this message]
2017-08-24 21:27       ` Matthew Weber
2017-08-25  1:47         ` Bin Meng
2017-08-29 14:26           ` Bin Meng
2017-08-29 15:37             ` Thomas Petazzoni
2017-08-30  9:25               ` Bin Meng
2017-08-30  9:31                 ` Thomas Petazzoni

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=20170824230211.4c0ea814@windsurf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox