public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jan Vrany <jan.vrany@fit.cvut.cz>
To: Jim Wilson <jimw@sifive.com>, hilihui@sina.com
Cc: gdb <gdb@sourceware.org>
Subject: Re: Re: Re: I compile gdbserver for RISCV on gdb10.1 version, and there is a error
Date: Thu, 19 Nov 2020 12:12:06 +0000	[thread overview]
Message-ID: <10c2901c0bb0281c08c780d4baf2143feed1f3a6.camel@fit.cvut.cz> (raw)
In-Reply-To: <CAFyWVaaszDY-D0fLKP5WSNOUhKqm+7EVCd=_08aM_G2T54vyqw@mail.gmail.com>

On Wed, 2020-11-18 at 17:04 -0800, Jim Wilson wrote:
> On Mon, Nov 16, 2020 at 6:07 PM <hilihui@sina.com> wrote:
> 
> > Where is your patches?
> > 
> 
> In the upstream linux kernel.  But they were added in Summer/Fall
> 2018.  If
> you have an old linux kernel release, then you won't have them.  They
> should be in the linux kernel mailing list, but I don't know of an
> easy way
> to search that offhand.  If you do a git log on a recent linux kernel
> clone
> and then look for jimw@sifive.com you will see 4 patches.  The first
> one,
> futex, was for glibc.  The other 3 are for gdb.  You can then use git
> diff
> to extract the patches.  Or cherry-pick them or whatever.

https://github.com/janvrany/riscv-linux/tree/users/jv/riscv-linux-4.15

Here you may find an 4.15 kernel with patches Jim is refering to
applied (I think), except the one for floating point regs. This is an
old kernel I used in fall of 2018. Was usable on QEMU and SiFive
Unleashed with debian. 

The repo also contains 5.0rc known to work just fine on Unleashed (with
debian) Indeed, these are fairly old kernels...
 
HTH, Jan

> 
> Jim


      reply	other threads:[~2020-11-19 12:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201117020745.B044518C0098@webmail.sinamail.sina.com.cn>
2020-11-19  1:04 ` Jim Wilson
2020-11-19 12:12   ` Jan Vrany [this message]

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=10c2901c0bb0281c08c780d4baf2143feed1f3a6.camel@fit.cvut.cz \
    --to=jan.vrany@fit.cvut.cz \
    --cc=gdb@sourceware.org \
    --cc=hilihui@sina.com \
    --cc=jimw@sifive.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).