From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 9158C21A16EFF for ; Tue, 30 May 2017 20:34:40 -0700 (PDT) Received: by mail-io0-x22e.google.com with SMTP id f102so7876874ioi.2 for ; Tue, 30 May 2017 20:35:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=XmO8b8NMnTZWIZKAEqr37/rQWiWmlXBRqTw3eeBp88M=; b=n9zNovbaTj2HrvLOT9Xkb9rGXmz0GlSpWRlXxui17sx9e9+Nos53gRP8V7yYN9woAF E2Yj0VwDi+WpFUspQg2WrD4XCTlEC4btqcZvxrER97r2tSN7u0C/1M0GuRNofHMmITYB +XzjiVjwQ07uIFJB6SXTJq/bZQabJz9QUU18p2C/kAMoYy1snNkoyrKR/1BAncA4Er7p fmyVoaLpXBJeyX9u1loXecegB7mRmF49jdrqxv07he4BDGHwniLZ/Ky8fbRC2iM+RkU0 irsTYXUenHEnI3PklcjlMBsW1LHmdwsvpguHWmw7Pw3hqmXI0ZTjGyCnUinDTAIV/syJ MLiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=XmO8b8NMnTZWIZKAEqr37/rQWiWmlXBRqTw3eeBp88M=; b=LWZ5GpNKnkYjOUjVp2gCy2S/c+RpfK+l5jRrzAzsf0ahoh7d9qKiO0PqIqYG4Wv/t+ bLmWvnVj5DlLLOjk7ZUHHbpYEcltf0pj/JGzHmBtvSnP5kBVqXAYXyssJtH0LIw1GTHa DbaTCvjcNCX6ppGmB2V9/V7bbLJcflkrXMEKrpKziw6AIMHhVMhGJfjPt+XqgIuP6Jjq 8fHrgTx8w2pLzSZpWitvlLBkADC9WP19tzTWex0xefJ2e9V97JhbETVyGLeiUe4V2sL/ zB1mlu0/83qa7TL3oPPtWeZj2ql+maN72WwtEv3wZ7W1oyN/JGoT1wZnBlkcoFea8LrM Qh6A== X-Gm-Message-State: AODbwcCDBZlyDdTylqxwqz0GyikwPPmFkNY1DeQLhNCQDhDV3l3rJa8s SHMngFeD9Ln7Dz1+RajNoFWDL22cgQ== X-Received: by 10.157.11.174 with SMTP id 43mr12953519oth.144.1496201739809; Tue, 30 May 2017 20:35:39 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: GN Keshava Date: Wed, 31 May 2017 03:35:28 +0000 Message-ID: To: "Carsey, Jaben" , "edk2-devel@lists.01.org" X-Content-Filtered-By: Mailman/MimeDel 2.1.22 Subject: Re: Unmount and mount a mass storage from shell X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 May 2017 03:34:40 -0000 Content-Type: text/plain; charset="UTF-8" Hi Jaben, Thanks a lot for your input. As I have mentioned in previous mail, I'm facing an issue now, that, If I reconnect my client device, the mass storage is not able to mount again automatically. Here is few more details. Expecting some help on this : I connect the the client device to UEFI host. I get the mass storage successfully. (device is listed as Mass storage in devices command) The client device also has serial CDC functionality (It is Linux CDC gadget, which will enumerate as both Mass storage (FAT32) and CDC serial com port). To use serial port, I have developed a custom serial driver. I use VID PID of the device in this custom driver to bind the driver to the device. I load this driver, and I get serial port (It is listed in sermode command) Now I refresh the mapping using map -r. Still I get the mass storage of device, and I'm able to access it correctly. Now I disconnect the client from host (UEFI) by unplugging the device. When I connect the device again, I'm not able to get Mass storage if i run map -r. But serial port will start to work fine again. If I run devices command, it is not shown as mass storage. but as linux gadget. Now if I use disconnect command, and followed by connect command to this device with mass storage driver, I'm able to mount the mass storage and use it. The issue is present if I load my serial driver, which uses device's VID PID. If I unload this driver and do the unplug-plug, I'm able to get mass storage automatically.. What could be the issue? Is there any way to solve this? (sorry for long post, it's difficult to explain otherwise) Thanks again. Regards, Keshava On Tue, 30 May 2017 at 20:56 Carsey, Jaben wrote: > I think that you will always need to inform the UEFI Shell of the change. > It is not designed to automatically do detection of added/removed/changed > devices. > > > > I think that your solution to use the code from mount makes the most sense. > > > > -Jaben > > > > *From:* GN Keshava [mailto:keshava.gn@gmail.com] > *Sent:* Thursday, May 25, 2017 11:02 PM > *To:* Carsey, Jaben ; edk2-devel@lists.01.org > *Subject:* Re: [edk2] Unmount and mount a mass storage from shell > *Importance:* High > > > > Hi Jaben, Thanks a lot for input. My necessity for unmount-mount is that, > the USB client is a Linux storage gadget, which needs to be remounted to > get the updated/new files created by Linux. Anyhow, now I'm doing this > programmatically by copying mount command code from older shell. :) > > > > One more issue is that, after Linux updates some file (on client side, > Linux will mount the same partition, save some file, and then umount the > partition. Then if i remount the partition on Host side, when host is > windows, i will get updated files) I will manually remove and connect the > cable (MS device), UEFI is not able to detect the MS itself. (This issue > observed, regardless of remount. This issue is not there on windows 10 > host). > > Can you give some pointers on this? > > > > Thanks a lot, Jaben. > > > > Regards, > > Keshava > > > > On Thu, 25 May 2017 at 21:26 Carsey, Jaben wrote: > > You can "disconnect" the driver > You can do "map -d" to delete a mapping > > I am unsure what your goals are for mount/unmount > > -Jaben > > > -----Original Message----- > > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of > > GN Keshava > > Sent: Wednesday, May 24, 2017 10:59 PM > > To: edk2-devel@lists.01.org > > Subject: [edk2] Unmount and mount a mass storage from shell > > Importance: High > > > > How can I unmount and mount a mass storage fs from UEFI shell? > > > > In older EFI shells, I can do with "mount" command. But it just does > > "mapping" in newer shell. It doesn't actually remounting the device. > > > > Please help. > > > > thanks > > _______________________________________________ > > edk2-devel mailing list > > edk2-devel@lists.01.org > > https://lists.01.org/mailman/listinfo/edk2-devel > >