All of lore.kernel.org
 help / color / mirror / Atom feed
* meta-ingrasys patches required for new merged drivers
@ 2019-04-19 19:43 Patrick Venture
       [not found] ` <BYAPR02MB58478B07866A63D01DA3EB25AE210@BYAPR02MB5847.namprd02.prod.outlook.com>
  0 siblings, 1 reply; 6+ messages in thread
From: Patrick Venture @ 2019-04-19 19:43 UTC (permalink / raw)
  To: Joel Stanley, Brad Bishop, Andrew Jeffery; +Cc: OpenBMC Maillist

If you don't work on or maintain meta-ingrasys/meta-zaius you can stop
reading and go on with your Friday. :D

All;

https://gerrit.openbmc-project.xyz/20692 and below are all ready-to-go
and some are required for the meta-aspeed bump staged for
openbmc/openbmc.

I wanted to throw this into an email to it jumps out more.

Patrick

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Seeking openbmc programmer's editor info
       [not found]     ` <BYAPR02MB5847D889707010DEF7F58A95AE220@BYAPR02MB5847.namprd02.prod.outlook.com>
@ 2019-04-22 16:16       ` Patrick Venture
  2019-04-22 16:21         ` Mark Brown
  0 siblings, 1 reply; 6+ messages in thread
From: Patrick Venture @ 2019-04-22 16:16 UTC (permalink / raw)
  To: Mark Brown; +Cc: OpenBMC Maillist

+ openbmc mailing list

On Mon, Apr 22, 2019 at 9:11 AM Mark Brown <mkbrown32@hotmail.com> wrote:
>
> The openbmc build instructions state that Ubuntu 14
> should be used.
> Are you saying that you read, navigate, modify source code
> in a different development platform from the build ?

Yes, what documentation are you reading that says to use ubuntu 14?
It's likely just out of date.

>
> Also, someone else mentioned Vim/C-scope -- however, I experience
> many "cannot find file" errors and then hangs of the Term window
> under C-scope.

I don't use C-scope.

>
>
> ________________________________________
> From: Patrick Venture <venture@google.com>
> Sent: Monday, April 22, 2019 7:26 AM
> To: Mark Brown
> Subject: Re: Seeking openbmc programmer's editor info
>
> I don't use Ubuntu 14, but generally grep/sed/vim are used most.
>
> On Sat, Apr 20, 2019 at 5:30 PM Mark Brown <mkbrown32@hotmail.com> wrote:
> >
> > I am a firmware guy watching the traffic on this email list.
> > I am interested to know what programmer's editor is most useful,
> > under Ubuntu 14,
> > to navigate and read the source code here, perform multi-file searches,
> > and help find bugs.
> > Which editor is most commonly used here ?
> >
> > Mark
> >
> > ________________________________________
> > From: openbmc <openbmc-bounces+mkbrown32=hotmail.com@lists.ozlabs.org> on behalf of Patrick Venture <venture@google.com>
> > Sent: Friday, April 19, 2019 12:43 PM
> > To: Joel Stanley; Brad Bishop; Andrew Jeffery
> > Cc: OpenBMC Maillist
> > Subject: meta-ingrasys patches required for new merged drivers
> >
> > If you don't work on or maintain meta-ingrasys/meta-zaius you can stop
> > reading and go on with your Friday. :D
> >
> > All;
> >
> > https://gerrit.openbmc-project.xyz/20692 and below are all ready-to-go
> > and some are required for the meta-aspeed bump staged for
> > openbmc/openbmc.
> >
> > I wanted to throw this into an email to it jumps out more.
> >
> > Patrick

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Seeking openbmc programmer's editor info
  2019-04-22 16:16       ` Seeking openbmc programmer's editor info Patrick Venture
@ 2019-04-22 16:21         ` Mark Brown
  2019-04-22 18:03           ` Emily Shaffer
  0 siblings, 1 reply; 6+ messages in thread
From: Mark Brown @ 2019-04-22 16:21 UTC (permalink / raw)
  To: Patrick Venture; +Cc: OpenBMC Maillist

On the official github   openbmc/openbmc   page:

https://github.com/openbmc/openbmc
==================================================
1) Prerequisite
Ubuntu 14.04
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
Fedora 28
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake rpcgen
sudo dnf groupinstall "C Development Tools and Libraries"
==================================================

________________________________________
From: Patrick Venture <venture@google.com>
Sent: Monday, April 22, 2019 9:16 AM
To: Mark Brown
Cc: OpenBMC Maillist
Subject: Re: Seeking openbmc programmer's editor info

+ openbmc mailing list

On Mon, Apr 22, 2019 at 9:11 AM Mark Brown <mkbrown32@hotmail.com> wrote:
>
> The openbmc build instructions state that Ubuntu 14
> should be used.
> Are you saying that you read, navigate, modify source code
> in a different development platform from the build ?

Yes, what documentation are you reading that says to use ubuntu 14?
It's likely just out of date.

>
> Also, someone else mentioned Vim/C-scope -- however, I experience
> many "cannot find file" errors and then hangs of the Term window
> under C-scope.

I don't use C-scope.

>
>
> ________________________________________
> From: Patrick Venture <venture@google.com>
> Sent: Monday, April 22, 2019 7:26 AM
> To: Mark Brown
> Subject: Re: Seeking openbmc programmer's editor info
>
> I don't use Ubuntu 14, but generally grep/sed/vim are used most.
>
> On Sat, Apr 20, 2019 at 5:30 PM Mark Brown <mkbrown32@hotmail.com> wrote:
> >
> > I am a firmware guy watching the traffic on this email list.
> > I am interested to know what programmer's editor is most useful,
> > under Ubuntu 14,
> > to navigate and read the source code here, perform multi-file searches,
> > and help find bugs.
> > Which editor is most commonly used here ?
> >
> > Mark
> >
> > ________________________________________
> > From: openbmc <openbmc-bounces+mkbrown32=hotmail.com@lists.ozlabs.org> on behalf of Patrick Venture <venture@google.com>
> > Sent: Friday, April 19, 2019 12:43 PM
> > To: Joel Stanley; Brad Bishop; Andrew Jeffery
> > Cc: OpenBMC Maillist
> > Subject: meta-ingrasys patches required for new merged drivers
> >
> > If you don't work on or maintain meta-ingrasys/meta-zaius you can stop
> > reading and go on with your Friday. :D
> >
> > All;
> >
> > https://gerrit.openbmc-project.xyz/20692 and below are all ready-to-go
> > and some are required for the meta-aspeed bump staged for
> > openbmc/openbmc.
> >
> > I wanted to throw this into an email to it jumps out more.
> >
> > Patrick

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Seeking openbmc programmer's editor info
  2019-04-22 16:21         ` Mark Brown
@ 2019-04-22 18:03           ` Emily Shaffer
  2019-04-22 18:42             ` Mark Brown
  0 siblings, 1 reply; 6+ messages in thread
From: Emily Shaffer @ 2019-04-22 18:03 UTC (permalink / raw)
  To: Mark Brown; +Cc: Patrick Venture, OpenBMC Maillist

OpenBMC is cross-compiled to target the embedded chip that it will run
on (often an Aspeed or Nuvoton part). I really doubt anybody is doing
their coding on an AST2400 :) Those stale-Ubuntu-targeted instructions
might still work, and if they don't, please let us know which
libraries are missing.

I use a Debian derivative and Vim. However, it's worth noting that
openbmc/openbmc references a bunch of other Git repos. Bitbake will
pull these down and build for you, but if you want to edit anything,
you'll need to either check them out on your own or use devtool.

Can you paste the errors you're seeing with C-Scope? (I don't use it,
but the text of the error might help us suss out what's going wrong.)

By the way, even for questions like this, it's better to mail the
entire list than choose one person at random to ask in a direct email.
Later developers may have the same question and your email will help
answer it for them. :)

Welcome to the project!

On Mon, Apr 22, 2019 at 9:22 AM Mark Brown <mkbrown32@hotmail.com> wrote:
>
> On the official github   openbmc/openbmc   page:
>
> https://github.com/openbmc/openbmc
> ==================================================
> 1) Prerequisite
> Ubuntu 14.04
> sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
> Fedora 28
> sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake rpcgen
> sudo dnf groupinstall "C Development Tools and Libraries"
> ==================================================
>
> ________________________________________
> From: Patrick Venture <venture@google.com>
> Sent: Monday, April 22, 2019 9:16 AM
> To: Mark Brown
> Cc: OpenBMC Maillist
> Subject: Re: Seeking openbmc programmer's editor info
>
> + openbmc mailing list
>
> On Mon, Apr 22, 2019 at 9:11 AM Mark Brown <mkbrown32@hotmail.com> wrote:
> >
> > The openbmc build instructions state that Ubuntu 14
> > should be used.
> > Are you saying that you read, navigate, modify source code
> > in a different development platform from the build ?
>
> Yes, what documentation are you reading that says to use ubuntu 14?
> It's likely just out of date.
>
> >
> > Also, someone else mentioned Vim/C-scope -- however, I experience
> > many "cannot find file" errors and then hangs of the Term window
> > under C-scope.
>
> I don't use C-scope.
>
> >
> >
> > ________________________________________
> > From: Patrick Venture <venture@google.com>
> > Sent: Monday, April 22, 2019 7:26 AM
> > To: Mark Brown
> > Subject: Re: Seeking openbmc programmer's editor info
> >
> > I don't use Ubuntu 14, but generally grep/sed/vim are used most.
> >
> > On Sat, Apr 20, 2019 at 5:30 PM Mark Brown <mkbrown32@hotmail.com> wrote:
> > >
> > > I am a firmware guy watching the traffic on this email list.
> > > I am interested to know what programmer's editor is most useful,
> > > under Ubuntu 14,
> > > to navigate and read the source code here, perform multi-file searches,
> > > and help find bugs.
> > > Which editor is most commonly used here ?
> > >
> > > Mark
> > >
> > > ________________________________________
> > > From: openbmc <openbmc-bounces+mkbrown32=hotmail.com@lists.ozlabs.org> on behalf of Patrick Venture <venture@google.com>
> > > Sent: Friday, April 19, 2019 12:43 PM
> > > To: Joel Stanley; Brad Bishop; Andrew Jeffery
> > > Cc: OpenBMC Maillist
> > > Subject: meta-ingrasys patches required for new merged drivers
> > >
> > > If you don't work on or maintain meta-ingrasys/meta-zaius you can stop
> > > reading and go on with your Friday. :D
> > >
> > > All;
> > >
> > > https://gerrit.openbmc-project.xyz/20692 and below are all ready-to-go
> > > and some are required for the meta-aspeed bump staged for
> > > openbmc/openbmc.
> > >
> > > I wanted to throw this into an email to it jumps out more.
> > >
> > > Patrick



-- 
Emily Shaffer

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Seeking openbmc programmer's editor info
  2019-04-22 18:03           ` Emily Shaffer
@ 2019-04-22 18:42             ` Mark Brown
  2019-05-02  3:48               ` Andrew Jeffery
  0 siblings, 1 reply; 6+ messages in thread
From: Mark Brown @ 2019-04-22 18:42 UTC (permalink / raw)
  To: Emily Shaffer; +Cc: Patrick Venture, OpenBMC Maillist

Thanks for your response.
Are there updated openbmc build instructions that the new developer
should follow, posted elsewhere ?

Here is the C-scope errors paste, 
I sent to someone else here but,  you are right,
it is unclear whether someone who may post here pervasively
is more of an administrative person (e.g. git project manager) ,
and may not be familiar with the issue raised.

===================================================================
===================================================================
Cscope 15.8a   generated a lot of errors -- maybe Vim  7.4.52   
is not compatible with Ubuntu 14.04.6 .
Any ideas ?
=================================================================
=================================================================
markbmc@markbmc-Precision-5520:~$
markbmc@markbmc-Precision-5520:~$ wget -P ~/.vim/plugin http://cscope.sourceforge.net/cscope_maps.vim
--2019-04-18 01:09:51--  http://cscope.sourceforge.net/cscope_maps.vim
Resolving cscope.sourceforge.net (cscope.sourceforge.net)... 216.105.38.10
Connecting to cscope.sourceforge.net (cscope.sourceforge.net)|216.105.38.10|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7336 (7.2K)
Saving to: ‘/home/markbmc/.vim/plugin/cscope_maps.vim’

100%[==============================================================================>] 7,336       --.-K/s   in 0s

2019-04-18 01:09:51 (1.21 GB/s) - ‘/home/markbmc/.vim/plugin/cscope_maps.vim’ saved [7336/7336]

markbmc@markbmc-Precision-5520:~$
markbmc@markbmc-Precision-5520:~$
markbmc@markbmc-Precision-5520:~$
markbmc@markbmc-Precision-5520:~$ cd openbmc
markbmc@markbmc-Precision-5520:~/openbmc$
markbmc@markbmc-Precision-5520:~/openbmc$
markbmc@markbmc-Precision-5520:~/openbmc$
markbmc@markbmc-Precision-5520:~/openbmc$ find . -type f -print | grep -E '\.(c(pp)?|h)$' > cscope.files
markbmc@markbmc-Precision-5520:~/openbmc$ ls -la
total 124420
drwxrwxr-x 29 markbmc markbmc      4096 Apr 18 01:30 .
drwxr-xr-x 22 markbmc markbmc      4096 Apr 18 01:01 ..
lrwxrwxrwx  1 markbmc markbmc        13 Apr 11 09:45 bitbake -> poky/bitbake/
drwxrwxr-x  7 markbmc markbmc      4096 Apr 11 13:35 build
-rw-rw-r--  1 markbmc markbmc 127253925 Apr 18 01:42 cscope.files
drwxrwxr-x  8 markbmc markbmc      4096 Apr 11 13:21 .git
drwxrwxr-x  2 markbmc markbmc      4096 Apr 11 09:45 .github
-rw-rw-r--  1 markbmc markbmc        31 Apr 11 09:45 .gitignore
-rw-rw-r--  1 markbmc markbmc       101 Apr 11 09:45 .gitreview
lrwxrwxrwx  1 markbmc markbmc        12 Apr 11 09:45 LICENSE -> poky/LICENSE
-rw-rw-r--  1 markbmc markbmc      2000 Apr 11 09:45 MAINTAINERS
lrwxrwxrwx  1 markbmc markbmc         9 Apr 11 09:45 meta -> poky/meta
drwxrwxr-x  4 markbmc markbmc      4096 Apr 11 09:45 meta-arm
drwxrwxr-x  6 markbmc markbmc      4096 Apr 11 09:45 meta-aspeed
drwxrwxr-x  7 markbmc markbmc      4096 Apr 11 09:45 meta-evb
drwxrwxr-x  4 markbmc markbmc      4096 Apr 11 09:45 meta-facebook
drwxrwxr-x  5 markbmc markbmc      4096 Apr 11 09:45 meta-google
drwxrwxr-x  4 markbmc markbmc      4096 Apr 11 09:45 meta-hxt
drwxrwxr-x  9 markbmc markbmc      4096 Apr 11 09:45 meta-ibm
drwxrwxr-x  4 markbmc markbmc      4096 Apr 11 09:45 meta-ingrasys
drwxrwxr-x  5 markbmc markbmc      4096 Apr 11 09:45 meta-inspur
drwxrwxr-x  5 markbmc markbmc      4096 Apr 11 09:45 meta-intel
drwxrwxr-x  4 markbmc markbmc      4096 Apr 11 09:45 meta-inventec
drwxrwxr-x  4 markbmc markbmc      4096 Apr 11 09:45 meta-mellanox
drwxrwxr-x  5 markbmc markbmc      4096 Apr 11 09:45 meta-nuvoton
drwxrwxr-x 14 markbmc markbmc      4096 Apr 11 09:45 meta-openembedded
drwxrwxr-x  6 markbmc markbmc      4096 Apr 11 09:45 meta-openpower
drwxrwxr-x 15 markbmc markbmc      4096 Apr 11 09:45 meta-phosphor
lrwxrwxrwx  1 markbmc markbmc        15 Apr 11 09:45 meta-poky -> poky/meta-poky/
drwxrwxr-x  3 markbmc markbmc      4096 Apr 11 09:45 meta-portwell
drwxrwxr-x  4 markbmc markbmc      4096 Apr 11 09:45 meta-qualcomm
drwxrwxr-x  7 markbmc markbmc      4096 Apr 11 09:45 meta-quanta
drwxrwxr-x 17 markbmc markbmc      4096 Apr 11 09:45 meta-raspberrypi
drwxrwxr-x 14 markbmc markbmc      4096 Apr 11 09:45 meta-security
lrwxrwxrwx  1 markbmc markbmc        18 Apr 11 09:45 meta-skeleton -> poky/meta-skeleton
drwxrwxr-x  3 markbmc markbmc      4096 Apr 11 09:45 meta-x86
drwxrwxr-x  5 markbmc markbmc      4096 Apr 11 09:45 meta-xilinx
lrwxrwxrwx  1 markbmc markbmc        22 Apr 11 09:45 oe-init-build-env -> poky/oe-init-build-env
-rw-rw-r--  1 markbmc markbmc       327 Apr 11 09:45 openbmc-env
drwxrwxr-x 10 markbmc markbmc      4096 Apr 11 09:45 poky
-rw-rw-r--  1 markbmc markbmc      4177 Apr 11 09:45 README.md
lrwxrwxrwx  1 markbmc markbmc        13 Apr 11 09:45 scripts -> poky/scripts/
-rwxrwxr-x  1 markbmc markbmc      1609 Apr 11 09:45 setup
-rw-rw-r--  1 markbmc markbmc        49 Apr 11 09:45 .templateconf
markbmc@markbmc-Precision-5520:~/openbmc$
markbmc@markbmc-Precision-5520:~/openbmc$
markbmc@markbmc-Precision-5520:~/openbmc$
markbmc@markbmc-Precision-5520:~/openbmc$ cscope -bq
cscope: cannot find file build/tmp/work/armv6-openbmc-linux-gnueabi/phosphor-debug-collector/1.0+gitAUTOINC+fa180596fe-r1/packages-split/phosphor-debug-collector-src/usr/src/debug/phosphor-debug-collector/1.0+gitAUTOINC+fa180596fe-r1/build/xyz/openbmc_project/Dump/Internal
cscope: cannot find file /Create/server.cpp
cscope: cannot find file build/tmp/work/armv6-openbmc-linux-gnueabi/openpower-debug-collector/1.0+gitAUTOINC+b618ccbaa7-r1/packages-split/openpower-debug-collector-src/usr/src/debug/openpower-debug-collector/1.0+gitAUTOINC+b618ccbaa7-r1/build/org/open_power/Host/Boot/error
cscope: cannot find file .cpp
cscope: cannot find file build/tmp/work/armv6-openbmc-linux-gnueabi/phosphor-led-manager/1.0+gitAUTOINC+ab3b247f04-r1/packages-split/phosphor-led-manager-src/usr/src/debug/phosphor-led-manager/1.0+gitAUTOINC+ab3b247f04-r1/build/fault-monitor/xyz/openbmc_project/Led/Fru/Mon
cscope: cannot find file itor/error.cpp
cscope: cannot find file build/tmp/work/armv6-openbmc-linux-gnueabi/phosphor-led-manager/1.0+gitAUTOINC+ab3b247f04-r1/packages-split/phosphor-led-manager-src/usr/src/debug/phosphor-led-manager/1.0+gitAUTOINC+ab3b247f04-r1/build/fault-monitor/xyz/openbmc_project/Led/Mapper
cscope: cannot find file error.cpp
cscope: cannot find file build/tmp/work/x86_64-linux/gcc-cross-arm/8.3.0-r0/image/home/markbmc/openbmc/build/tmp/work/x86_64-linux/gcc-cross-arm/8.3.0-r0/recipe-sysroot-native/usr/lib/arm-openbmc-linux-gnueabi/gcc/arm-openbmc-linux-gnueabi/8.3.0/plugin/include/gimple-build
cscope: cannot find file er.h
cscope: cannot find file build/tmp/work/x86_64-linux/gcc-cross-arm/8.3.0-r0/image/home/markbmc/openbmc/build/tmp/work/x86_64-linux/gcc-cross-arm/8.3.0-r0/recipe-sysroot-native/usr/lib/arm-openbmc-linux-gnueabi/gcc/arm-openbmc-linux-gnueabi/8.3.0/plugin/include/gt-fortran-t
cscope: cannot find file rans-stmt.h
cscope: cannot find file build/tmp/work/x86_64-linux/gcc-cross-arm/8.3.0-r0/image/home/markbmc/openbmc/build/tmp/work/x86_64-linux/gcc-cross-arm/8.3.0-r0/recipe-sysroot-native/usr/lib/arm-openbmc-linux-gnueabi/gcc/arm-openbmc-linux-gnueabi/8.3.0/plugin/include/gt-cp-method
cscope: cannot find file .h
cscope: cannot find file build/tmp/work/x86_64-linux/gcc-cross-arm/8.3.0-r0/image/home/markbmc/openbmc/build/tmp/work/x86_64-linux/gcc-cross-arm/8.3.0-r0/recipe-sysroot-native/usr/lib/arm-openbmc-linux-gnueabi/gcc/arm-openbmc-linux-gnueabi/8.3.0/plugin/include/cp/name-look
...
...
=================================================================
=================================================================

________________________________________
From: Emily Shaffer <emilyshaffer@google.com>
Sent: Monday, April 22, 2019 11:03 AM
To: Mark Brown
Cc: Patrick Venture; OpenBMC Maillist
Subject: Re: Seeking openbmc programmer's editor info

OpenBMC is cross-compiled to target the embedded chip that it will run
on (often an Aspeed or Nuvoton part). I really doubt anybody is doing
their coding on an AST2400 :) Those stale-Ubuntu-targeted instructions
might still work, and if they don't, please let us know which
libraries are missing.

I use a Debian derivative and Vim. However, it's worth noting that
openbmc/openbmc references a bunch of other Git repos. Bitbake will
pull these down and build for you, but if you want to edit anything,
you'll need to either check them out on your own or use devtool.

Can you paste the errors you're seeing with C-Scope? (I don't use it,
but the text of the error might help us suss out what's going wrong.)

By the way, even for questions like this, it's better to mail the
entire list than choose one person at random to ask in a direct email.
Later developers may have the same question and your email will help
answer it for them. :)

Welcome to the project!

On Mon, Apr 22, 2019 at 9:22 AM Mark Brown <mkbrown32@hotmail.com> wrote:
>
> On the official github   openbmc/openbmc   page:
>
> https://github.com/openbmc/openbmc
> ==================================================
> 1) Prerequisite
> Ubuntu 14.04
> sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
> Fedora 28
> sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake rpcgen
> sudo dnf groupinstall "C Development Tools and Libraries"
> ==================================================
>
> ________________________________________
> From: Patrick Venture <venture@google.com>
> Sent: Monday, April 22, 2019 9:16 AM
> To: Mark Brown
> Cc: OpenBMC Maillist
> Subject: Re: Seeking openbmc programmer's editor info
>
> + openbmc mailing list
>
> On Mon, Apr 22, 2019 at 9:11 AM Mark Brown <mkbrown32@hotmail.com> wrote:
> >
> > The openbmc build instructions state that Ubuntu 14
> > should be used.
> > Are you saying that you read, navigate, modify source code
> > in a different development platform from the build ?
>
> Yes, what documentation are you reading that says to use ubuntu 14?
> It's likely just out of date.
>
> >
> > Also, someone else mentioned Vim/C-scope -- however, I experience
> > many "cannot find file" errors and then hangs of the Term window
> > under C-scope.
>
> I don't use C-scope.
>
> >
> >
> > ________________________________________
> > From: Patrick Venture <venture@google.com>
> > Sent: Monday, April 22, 2019 7:26 AM
> > To: Mark Brown
> > Subject: Re: Seeking openbmc programmer's editor info
> >
> > I don't use Ubuntu 14, but generally grep/sed/vim are used most.
> >
> > On Sat, Apr 20, 2019 at 5:30 PM Mark Brown <mkbrown32@hotmail.com> wrote:
> > >
> > > I am a firmware guy watching the traffic on this email list.
> > > I am interested to know what programmer's editor is most useful,
> > > under Ubuntu 14,
> > > to navigate and read the source code here, perform multi-file searches,
> > > and help find bugs.
> > > Which editor is most commonly used here ?
> > >
> > > Mark
> > >
> > > ________________________________________
> > > From: openbmc <openbmc-bounces+mkbrown32=hotmail.com@lists.ozlabs.org> on behalf of Patrick Venture <venture@google.com>
> > > Sent: Friday, April 19, 2019 12:43 PM
> > > To: Joel Stanley; Brad Bishop; Andrew Jeffery
> > > Cc: OpenBMC Maillist
> > > Subject: meta-ingrasys patches required for new merged drivers
> > >
> > > If you don't work on or maintain meta-ingrasys/meta-zaius you can stop
> > > reading and go on with your Friday. :D
> > >
> > > All;
> > >
> > > https://gerrit.openbmc-project.xyz/20692 and below are all ready-to-go
> > > and some are required for the meta-aspeed bump staged for
> > > openbmc/openbmc.
> > >
> > > I wanted to throw this into an email to it jumps out more.
> > >
> > > Patrick



--
Emily Shaffer

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Seeking openbmc programmer's editor info
  2019-04-22 18:42             ` Mark Brown
@ 2019-05-02  3:48               ` Andrew Jeffery
  0 siblings, 0 replies; 6+ messages in thread
From: Andrew Jeffery @ 2019-05-02  3:48 UTC (permalink / raw)
  To: Mark Brown, Emily Shaffer; +Cc: Patrick Venture, OpenBMC Maillist



On Tue, 23 Apr 2019, at 04:14, Mark Brown wrote:
> Thanks for your response.
> Are there updated openbmc build instructions that the new developer
> should follow, posted elsewhere ?
> 
> Here is the C-scope errors paste, 
> I sent to someone else here but,  you are right,
> it is unclear whether someone who may post here pervasively
> is more of an administrative person (e.g. git project manager) ,
> and may not be familiar with the issue raised.

When I suggested cscope I did so in the (probably implicit) context of navigating
the C and C++ code that makes up OpenBMC. cscope does not support navigating
bitbake recipes as far as I'm aware. Your best tools there are `git ls-files` and
`git grep`. Note that the C and C++ code all resides in separate repos that are
pointed to by the bitbake recipes.

I hope that clarifies, sorry for any confusion.

Andrew

> 
> ===================================================================
> ===================================================================
> Cscope 15.8a   generated a lot of errors -- maybe Vim  7.4.52   
> is not compatible with Ubuntu 14.04.6 .
> Any ideas ?
> =================================================================
> =================================================================
> markbmc@markbmc-Precision-5520:~$
> markbmc@markbmc-Precision-5520:~$ wget -P ~/.vim/plugin 
> http://cscope.sourceforge.net/cscope_maps.vim
> --2019-04-18 01:09:51--  http://cscope.sourceforge.net/cscope_maps.vim
> Resolving cscope.sourceforge.net (cscope.sourceforge.net)... 
> 216.105.38.10
> Connecting to cscope.sourceforge.net 
> (cscope.sourceforge.net)|216.105.38.10|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 7336 (7.2K)
> Saving to: ‘/home/markbmc/.vim/plugin/cscope_maps.vim’
> 
> 100%[==============================================================================>] 7,336       --.-K/s   in 0s
> 
> 2019-04-18 01:09:51 (1.21 GB/s) - 
> ‘/home/markbmc/.vim/plugin/cscope_maps.vim’ saved [7336/7336]
> 
> markbmc@markbmc-Precision-5520:~$
> markbmc@markbmc-Precision-5520:~$
> markbmc@markbmc-Precision-5520:~$
> markbmc@markbmc-Precision-5520:~$ cd openbmc
> markbmc@markbmc-Precision-5520:~/openbmc$
> markbmc@markbmc-Precision-5520:~/openbmc$
> markbmc@markbmc-Precision-5520:~/openbmc$
> markbmc@markbmc-Precision-5520:~/openbmc$ find . -type f -print | grep 
> -E '\.(c(pp)?|h)$' > cscope.files
> markbmc@markbmc-Precision-5520:~/openbmc$ ls -la
> total 124420
> drwxrwxr-x 29 markbmc markbmc      4096 Apr 18 01:30 .
> drwxr-xr-x 22 markbmc markbmc      4096 Apr 18 01:01 ..
> lrwxrwxrwx  1 markbmc markbmc        13 Apr 11 09:45 bitbake -> 
> poky/bitbake/
> drwxrwxr-x  7 markbmc markbmc      4096 Apr 11 13:35 build
> -rw-rw-r--  1 markbmc markbmc 127253925 Apr 18 01:42 cscope.files
> drwxrwxr-x  8 markbmc markbmc      4096 Apr 11 13:21 .git
> drwxrwxr-x  2 markbmc markbmc      4096 Apr 11 09:45 .github
> -rw-rw-r--  1 markbmc markbmc        31 Apr 11 09:45 .gitignore
> -rw-rw-r--  1 markbmc markbmc       101 Apr 11 09:45 .gitreview
> lrwxrwxrwx  1 markbmc markbmc        12 Apr 11 09:45 LICENSE -> 
> poky/LICENSE
> -rw-rw-r--  1 markbmc markbmc      2000 Apr 11 09:45 MAINTAINERS
> lrwxrwxrwx  1 markbmc markbmc         9 Apr 11 09:45 meta -> poky/meta
> drwxrwxr-x  4 markbmc markbmc      4096 Apr 11 09:45 meta-arm
> drwxrwxr-x  6 markbmc markbmc      4096 Apr 11 09:45 meta-aspeed
> drwxrwxr-x  7 markbmc markbmc      4096 Apr 11 09:45 meta-evb
> drwxrwxr-x  4 markbmc markbmc      4096 Apr 11 09:45 meta-facebook
> drwxrwxr-x  5 markbmc markbmc      4096 Apr 11 09:45 meta-google
> drwxrwxr-x  4 markbmc markbmc      4096 Apr 11 09:45 meta-hxt
> drwxrwxr-x  9 markbmc markbmc      4096 Apr 11 09:45 meta-ibm
> drwxrwxr-x  4 markbmc markbmc      4096 Apr 11 09:45 meta-ingrasys
> drwxrwxr-x  5 markbmc markbmc      4096 Apr 11 09:45 meta-inspur
> drwxrwxr-x  5 markbmc markbmc      4096 Apr 11 09:45 meta-intel
> drwxrwxr-x  4 markbmc markbmc      4096 Apr 11 09:45 meta-inventec
> drwxrwxr-x  4 markbmc markbmc      4096 Apr 11 09:45 meta-mellanox
> drwxrwxr-x  5 markbmc markbmc      4096 Apr 11 09:45 meta-nuvoton
> drwxrwxr-x 14 markbmc markbmc      4096 Apr 11 09:45 meta-openembedded
> drwxrwxr-x  6 markbmc markbmc      4096 Apr 11 09:45 meta-openpower
> drwxrwxr-x 15 markbmc markbmc      4096 Apr 11 09:45 meta-phosphor
> lrwxrwxrwx  1 markbmc markbmc        15 Apr 11 09:45 meta-poky -> 
> poky/meta-poky/
> drwxrwxr-x  3 markbmc markbmc      4096 Apr 11 09:45 meta-portwell
> drwxrwxr-x  4 markbmc markbmc      4096 Apr 11 09:45 meta-qualcomm
> drwxrwxr-x  7 markbmc markbmc      4096 Apr 11 09:45 meta-quanta
> drwxrwxr-x 17 markbmc markbmc      4096 Apr 11 09:45 meta-raspberrypi
> drwxrwxr-x 14 markbmc markbmc      4096 Apr 11 09:45 meta-security
> lrwxrwxrwx  1 markbmc markbmc        18 Apr 11 09:45 meta-skeleton -> 
> poky/meta-skeleton
> drwxrwxr-x  3 markbmc markbmc      4096 Apr 11 09:45 meta-x86
> drwxrwxr-x  5 markbmc markbmc      4096 Apr 11 09:45 meta-xilinx
> lrwxrwxrwx  1 markbmc markbmc        22 Apr 11 09:45 oe-init-build-env 
> -> poky/oe-init-build-env
> -rw-rw-r--  1 markbmc markbmc       327 Apr 11 09:45 openbmc-env
> drwxrwxr-x 10 markbmc markbmc      4096 Apr 11 09:45 poky
> -rw-rw-r--  1 markbmc markbmc      4177 Apr 11 09:45 README.md
> lrwxrwxrwx  1 markbmc markbmc        13 Apr 11 09:45 scripts -> 
> poky/scripts/
> -rwxrwxr-x  1 markbmc markbmc      1609 Apr 11 09:45 setup
> -rw-rw-r--  1 markbmc markbmc        49 Apr 11 09:45 .templateconf
> markbmc@markbmc-Precision-5520:~/openbmc$
> markbmc@markbmc-Precision-5520:~/openbmc$
> markbmc@markbmc-Precision-5520:~/openbmc$
> markbmc@markbmc-Precision-5520:~/openbmc$ cscope -bq
> cscope: cannot find file 
> build/tmp/work/armv6-openbmc-linux-gnueabi/phosphor-debug-collector/1.0+gitAUTOINC+fa180596fe-r1/packages-split/phosphor-debug-collector-src/usr/src/debug/phosphor-debug-collector/1.0+gitAUTOINC+fa180596fe-r1/build/xyz/openbmc_project/Dump/Internal
> cscope: cannot find file /Create/server.cpp
> cscope: cannot find file 
> build/tmp/work/armv6-openbmc-linux-gnueabi/openpower-debug-collector/1.0+gitAUTOINC+b618ccbaa7-r1/packages-split/openpower-debug-collector-src/usr/src/debug/openpower-debug-collector/1.0+gitAUTOINC+b618ccbaa7-r1/build/org/open_power/Host/Boot/error
> cscope: cannot find file .cpp
> cscope: cannot find file 
> build/tmp/work/armv6-openbmc-linux-gnueabi/phosphor-led-manager/1.0+gitAUTOINC+ab3b247f04-r1/packages-split/phosphor-led-manager-src/usr/src/debug/phosphor-led-manager/1.0+gitAUTOINC+ab3b247f04-r1/build/fault-monitor/xyz/openbmc_project/Led/Fru/Mon
> cscope: cannot find file itor/error.cpp
> cscope: cannot find file 
> build/tmp/work/armv6-openbmc-linux-gnueabi/phosphor-led-manager/1.0+gitAUTOINC+ab3b247f04-r1/packages-split/phosphor-led-manager-src/usr/src/debug/phosphor-led-manager/1.0+gitAUTOINC+ab3b247f04-r1/build/fault-monitor/xyz/openbmc_project/Led/Mapper
> cscope: cannot find file error.cpp
> cscope: cannot find file 
> build/tmp/work/x86_64-linux/gcc-cross-arm/8.3.0-r0/image/home/markbmc/openbmc/build/tmp/work/x86_64-linux/gcc-cross-arm/8.3.0-r0/recipe-sysroot-native/usr/lib/arm-openbmc-linux-gnueabi/gcc/arm-openbmc-linux-gnueabi/8.3.0/plugin/include/gimple-build
> cscope: cannot find file er.h
> cscope: cannot find file 
> build/tmp/work/x86_64-linux/gcc-cross-arm/8.3.0-r0/image/home/markbmc/openbmc/build/tmp/work/x86_64-linux/gcc-cross-arm/8.3.0-r0/recipe-sysroot-native/usr/lib/arm-openbmc-linux-gnueabi/gcc/arm-openbmc-linux-gnueabi/8.3.0/plugin/include/gt-fortran-t
> cscope: cannot find file rans-stmt.h
> cscope: cannot find file 
> build/tmp/work/x86_64-linux/gcc-cross-arm/8.3.0-r0/image/home/markbmc/openbmc/build/tmp/work/x86_64-linux/gcc-cross-arm/8.3.0-r0/recipe-sysroot-native/usr/lib/arm-openbmc-linux-gnueabi/gcc/arm-openbmc-linux-gnueabi/8.3.0/plugin/include/gt-cp-method
> cscope: cannot find file .h
> cscope: cannot find file 
> build/tmp/work/x86_64-linux/gcc-cross-arm/8.3.0-r0/image/home/markbmc/openbmc/build/tmp/work/x86_64-linux/gcc-cross-arm/8.3.0-r0/recipe-sysroot-native/usr/lib/arm-openbmc-linux-gnueabi/gcc/arm-openbmc-linux-gnueabi/8.3.0/plugin/include/cp/name-look
> ...
> ...
> =================================================================
> =================================================================
> 
> ________________________________________
> From: Emily Shaffer <emilyshaffer@google.com>
> Sent: Monday, April 22, 2019 11:03 AM
> To: Mark Brown
> Cc: Patrick Venture; OpenBMC Maillist
> Subject: Re: Seeking openbmc programmer's editor info
> 
> OpenBMC is cross-compiled to target the embedded chip that it will run
> on (often an Aspeed or Nuvoton part). I really doubt anybody is doing
> their coding on an AST2400 :) Those stale-Ubuntu-targeted instructions
> might still work, and if they don't, please let us know which
> libraries are missing.
> 
> I use a Debian derivative and Vim. However, it's worth noting that
> openbmc/openbmc references a bunch of other Git repos. Bitbake will
> pull these down and build for you, but if you want to edit anything,
> you'll need to either check them out on your own or use devtool.
> 
> Can you paste the errors you're seeing with C-Scope? (I don't use it,
> but the text of the error might help us suss out what's going wrong.)
> 
> By the way, even for questions like this, it's better to mail the
> entire list than choose one person at random to ask in a direct email.
> Later developers may have the same question and your email will help
> answer it for them. :)
> 
> Welcome to the project!
> 
> On Mon, Apr 22, 2019 at 9:22 AM Mark Brown <mkbrown32@hotmail.com> wrote:
> >
> > On the official github   openbmc/openbmc   page:
> >
> > https://github.com/openbmc/openbmc
> > ==================================================
> > 1) Prerequisite
> > Ubuntu 14.04
> > sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
> > Fedora 28
> > sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake rpcgen
> > sudo dnf groupinstall "C Development Tools and Libraries"
> > ==================================================
> >
> > ________________________________________
> > From: Patrick Venture <venture@google.com>
> > Sent: Monday, April 22, 2019 9:16 AM
> > To: Mark Brown
> > Cc: OpenBMC Maillist
> > Subject: Re: Seeking openbmc programmer's editor info
> >
> > + openbmc mailing list
> >
> > On Mon, Apr 22, 2019 at 9:11 AM Mark Brown <mkbrown32@hotmail.com> wrote:
> > >
> > > The openbmc build instructions state that Ubuntu 14
> > > should be used.
> > > Are you saying that you read, navigate, modify source code
> > > in a different development platform from the build ?
> >
> > Yes, what documentation are you reading that says to use ubuntu 14?
> > It's likely just out of date.
> >
> > >
> > > Also, someone else mentioned Vim/C-scope -- however, I experience
> > > many "cannot find file" errors and then hangs of the Term window
> > > under C-scope.
> >
> > I don't use C-scope.
> >
> > >
> > >
> > > ________________________________________
> > > From: Patrick Venture <venture@google.com>
> > > Sent: Monday, April 22, 2019 7:26 AM
> > > To: Mark Brown
> > > Subject: Re: Seeking openbmc programmer's editor info
> > >
> > > I don't use Ubuntu 14, but generally grep/sed/vim are used most.
> > >
> > > On Sat, Apr 20, 2019 at 5:30 PM Mark Brown <mkbrown32@hotmail.com> wrote:
> > > >
> > > > I am a firmware guy watching the traffic on this email list.
> > > > I am interested to know what programmer's editor is most useful,
> > > > under Ubuntu 14,
> > > > to navigate and read the source code here, perform multi-file searches,
> > > > and help find bugs.
> > > > Which editor is most commonly used here ?
> > > >
> > > > Mark
> > > >
> > > > ________________________________________
> > > > From: openbmc <openbmc-bounces+mkbrown32=hotmail.com@lists.ozlabs.org> on behalf of Patrick Venture <venture@google.com>
> > > > Sent: Friday, April 19, 2019 12:43 PM
> > > > To: Joel Stanley; Brad Bishop; Andrew Jeffery
> > > > Cc: OpenBMC Maillist
> > > > Subject: meta-ingrasys patches required for new merged drivers
> > > >
> > > > If you don't work on or maintain meta-ingrasys/meta-zaius you can stop
> > > > reading and go on with your Friday. :D
> > > >
> > > > All;
> > > >
> > > > https://gerrit.openbmc-project.xyz/20692 and below are all ready-to-go
> > > > and some are required for the meta-aspeed bump staged for
> > > > openbmc/openbmc.
> > > >
> > > > I wanted to throw this into an email to it jumps out more.
> > > >
> > > > Patrick
> 
> 
> 
> --
> Emily Shaffer
>

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2019-05-02  3:48 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-04-19 19:43 meta-ingrasys patches required for new merged drivers Patrick Venture
     [not found] ` <BYAPR02MB58478B07866A63D01DA3EB25AE210@BYAPR02MB5847.namprd02.prod.outlook.com>
     [not found]   ` <CAO=notzqWthZ29ghauXdzS7Y8WYeVrnMbbmz6Tgt=R6n_mRRAA@mail.gmail.com>
     [not found]     ` <BYAPR02MB5847D889707010DEF7F58A95AE220@BYAPR02MB5847.namprd02.prod.outlook.com>
2019-04-22 16:16       ` Seeking openbmc programmer's editor info Patrick Venture
2019-04-22 16:21         ` Mark Brown
2019-04-22 18:03           ` Emily Shaffer
2019-04-22 18:42             ` Mark Brown
2019-05-02  3:48               ` Andrew Jeffery

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.