public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Brian Foster <brian.foster@maximintegrated.com>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: [Q] `ubiattach: ioctl 0x40186f40 failed: Inappropriate ioctl for device' - What changed?
Date: Tue, 25 Feb 2014 17:01:18 +0100	[thread overview]
Message-ID: <4790760.yeQTJBGPZK@laclwks004> (raw)


Hello,

 Using an (admittedly ancient) BuildRoot v2010.11
 (which uses v2.6.36.4 kernel headers) with an
 (also admittedly ancient) v2.6.36.4 Linux kernel,
 ubiattach(1) works fine.  The ‘ubiattach’ is of
 vintage v1.4.6 (and has not been modified).

 However, using that _identical_ ‘ubiattach’ binary
 (which is for an ARM926EJ-S CPU) with a more recent
 v3.10.30 kernel, it fails.  For example:

    # ubiattach -m7 -d0 /dev/ubi_ctrl
    ubiattach: ioctl 0x40186f40 failed: Inappropriate ioctl for device
    #

 I assume the value of, and/or parameter to, some
 ioctl command has changed v2.6.36 → v3.10, but
 am at a loss as to just _what_ changed (or why).

 Any pointers would be appreciated.

cheers!
	-blf-

-- 
Brian Foster
Principal MTS, Software        |  La Ciotat, France
Maxim Integrated               |  http://www.maximintegrated.com/

             reply	other threads:[~2014-02-25 16:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 16:01 Brian Foster [this message]
2014-02-26  7:21 ` [Q] `ubiattach: ioctl 0x40186f40 failed: Inappropriate ioctl for device' - What changed? Brian Norris
2014-02-26  7:42   ` Brian Foster
     [not found]     ` <3384625.n7jGnVRFVi@laclwks004>
2014-02-26 18:00       ` SOLVED: " Brian Norris

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=4790760.yeQTJBGPZK@laclwks004 \
    --to=brian.foster@maximintegrated.com \
    --cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox