From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11011] New: BUildroot for Raspberry Pi 2
Date: Fri, 11 May 2018 14:13:37 +0000 [thread overview]
Message-ID: <bug-11011-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11011
Bug ID: 11011
Summary: BUildroot for Raspberry Pi 2
Product: buildroot
Version: 2018.02.1
Hardware: PC
OS: Linux
Status: NEW
Severity: critical
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: umamahesh.y at hcl.com
CC: buildroot at uclibc.org
Target Milestone: ---
Hi
I am running latest buildroot version (2018.02.1) with kernel version 4.14 on
Raspberry Pi 2, I am unable to up the i2c interface and RTC interface.
With i2cdetect -l it doesn't list anything.
RTC it fails to register with /dev/rtc.
There is no dev nodes for i2c and rtc created by default.
Please suggest.
I wanted i2c and rtc running asap.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2018-05-11 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-11 14:13 bugzilla at busybox.net [this message]
2018-05-11 15:32 ` [Buildroot] [Bug 11011] BUildroot for Raspberry Pi 2 bugzilla at busybox.net
2018-05-11 15:52 ` bugzilla at busybox.net
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=bug-11011-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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 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.