On Tue, Nov 22, 2011 at 03:47:41PM +, Nima Misaghian wrote:
> We have added firmware download command to atacontrol at work, for
> which I have attached a patch against 8.2 to this email.
>
> The format of the command is similar to the camcontrol counterpart:
>
> atacontrol fwdownload
>
>
---Original Message-
> From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-
> curr...@freebsd.org] On Behalf Of Pegasus Mc Cleaft
> Sent: Sunday, November 20, 2011 9:55 AM
> To: freebsd-current@freebsd.org
> Cc: an...@albsmeier.net; Nima Misaghian
> Subject: Re: Adding
On Sun, Nov 20, 2011 at 7:44 AM, Pegasus Mc Cleaft wrote:
> On Sunday 20 November 2011 15:24:41 Andriy Gapon wrote:
>> > I have tried issuing a TUR to all my drives to see if it was controller
>> > or drive specific, but all of them return the same error (The drives are
>> > Seagate, Hitachi and W
On Sunday 20 November 2011 15:24:41 Andriy Gapon wrote:
> > I have tried issuing a TUR to all my drives to see if it was controller
> > or drive specific, but all of them return the same error (The drives are
> > Seagate, Hitachi and WD).
> >
> > What am I doing wrong?
>
> You are sending SCSI co
on 20/11/2011 16:54 Pegasus Mc Cleaft said the following:
> Hi Nima,
>
> I have tried your latest patch against current, but I am having
> difficulty
> getting it to work. I was wondering, is this feature limited to SCSI drives?
> I have been trying it against my SATA drives but it look
Hi Nima,
I have tried your latest patch against current, but I am having
difficulty
getting it to work. I was wondering, is this feature limited to SCSI drives?
I have been trying it against my SATA drives but it looks like it is failing
on issuing a TUR.
IE:
feathers# camcontrol
Rodrigues
> Sent: Thursday, November 03, 2011 10:06 PM
> To: Nima Misaghian
> Cc: freebsd-current@freebsd.org
> Subject: Re: Adding disk firmware programming capability to camcontrol
>
> On Fri, Oct 28, 2011 at 1:47 PM, Nima Misaghian
> wrote:
> > Hi,
> >
> &
On 4 Nov 2011 16:33, "Pegasus Mc Cleaft" wrote:
>
> >>
> >>To me, the only difference between borking a drive because of
> >> bad firmware and typing "rm -rf *" from root is about £40. You still
> >> lose at least a day rebuilding/restoring everything.
> >>
> >
> >You clearly haven't boug
>>
>>To me, the only difference between borking a drive because of
>> bad firmware and typing "rm -rf *" from root is about £40. You still
>> lose at least a day rebuilding/restoring everything.
>>
>
>You clearly haven't bought a hard drive recently.
>
>Chris
Laughs!
Yea, trus
On 29 Oct 2011 00:38, "Pegasus Mc Cleaft" wrote:
>
> >> The linux hdparm program is so paranoid about this that you have to use
> >> extra arguments like "--yes-really-destroy-my-disk-drive" to do this.
> >
> >I concur. Loudly. The ability to brick your hardware is just too
> >large to not make p
On Thu, Nov 03, 2011 at 07:05:54PM -0700, Craig Rodrigues wrote:
> On Fri, Oct 28, 2011 at 1:47 PM, Nima Misaghian
> wrote:
> > Hi,
> >
> > I have got code developed by Andre Albsmeier that is capable of
> > programming firmware of hard drives from several vendors and ?turned
> > it into a camco
On Fri, Oct 28, 2011 at 1:47 PM, Nima Misaghian wrote:
> Hi,
>
> I have got code developed by Andre Albsmeier that is capable of
> programming firmware of hard drives from several vendors and turned
> it into a camcontrol command.
+1
I took a look at your patch and it looks great. I have worke
On Fri, Oct 28, 2011 at 4:37 PM, Pegasus Mc Cleaft wrote:
>>> The linux hdparm program is so paranoid about this that you have to use
>>> extra arguments like "--yes-really-destroy-my-disk-drive" to do this.
>>
>>I concur. Loudly. The ability to brick your hardware is just too
>>large to not make
On 10/28/11 3:43 PM, Lyndon Nerenberg (VE6BBM/VE7TFX) wrote:
The linux hdparm program is so paranoid about this that you have to use
extra arguments like "--yes-really-destroy-my-disk-drive" to do this.
I concur. Loudly. The ability to brick your hardware is just too
large to not make people go
>> The linux hdparm program is so paranoid about this that you have to use
>> extra arguments like "--yes-really-destroy-my-disk-drive" to do this.
>
>I concur. Loudly. The ability to brick your hardware is just too
>large to not make people go through the "I tell you three times"
>dance. It's n
> The linux hdparm program is so paranoid about this that you have to use
> extra arguments like "--yes-really-destroy-my-disk-drive" to do this.
I concur. Loudly. The ability to brick your hardware is just too
large to not make people go through the "I tell you three times"
dance. It's not lik
This is a good idea, except that it makes me really really nervous. I do
not believe that fw downloads are generic enough to encapsulate. I've
used camcontrol recently to tunnel an ATA command through mpt2 that does
an ATA DOWNLOAD FW (mode 7), but that is only because it is a specific
drive th
On Fri, Oct 28, 2011 at 1:47 PM, Nima Misaghian wrote:
> Hi,
>
> I have got code developed by Andre Albsmeier that is capable of
> programming firmware of hard drives from several vendors and turned
> it into a camcontrol command.
>
> The posted patch (against RELENG_8_2) basically adds the follo
Hi,
I have got code developed by Andre Albsmeier that is capable of
programming firmware of hard drives from several vendors and turned
it into a camcontrol command.
The posted patch (against RELENG_8_2) basically adds the following new
command to camcontrol:
camcontrol fwdownload [device id] [
Hi,
I have got code developed by Andre Albsmeier that is capable of
programming firmware of hard drives from several vendors and turned
it into a camcontrol command.
The posted patch (against RELENG_8_2) basically adds the following new
command to camcontrol:
camcontrol fwdownload [device id] [
20 matches
Mail list logo
