From: Oliver Graute <oliver.graute@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: remote kernel developing with arm soc board eval kit
Date: Sat, 7 Sep 2019 17:03:58 +0200 [thread overview]
Message-ID: <20190907150358.GA11054@portage> (raw)
Hello list,
I've a soc board on my desk in the office and would like to know what is
the best practice to do kernel development remotely with such a board.
In the office I can plug in sd-cards or switch power off which I can't
do if I'am not physically present. But I think with a tftp/nfs setup and
ssh/minicom I can do something in that direction.
So I would like to know how the real kernel developers build such a
setup and how they handle kernel panics without driving back to office
or call a collegue.
Best regards,
Oliver
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2019-09-07 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-07 15:03 Oliver Graute [this message]
2019-09-07 15:11 ` remote kernel developing with arm soc board eval kit Phi Nguyễn Đình
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=20190907150358.GA11054@portage \
--to=oliver.graute@gmail.com \
--cc=kernelnewbies@kernelnewbies.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.